Description of problem: When project viewer has view permission on more than one projects, he is unable to set web console homepage to any project overview page although he has view access Version-Release number of selected component (if applicable): v3.9.0-0.34.0 How reproducible: Always Steps to Reproduce: 1.user1 create two projects, test1 and test2. Grant user2 view permission on test1 first $ oc new-project test1 $ oc new-project test2 $ oc policy add-role-to-user view user2 -n test1 2.user2 login to web console,click Set Home page, choose "Overview Page for test1" and Save 3.Grant user2 view permission on test2 too. $ oc policy add-role-to-user view user2 -n test2 4.click Set Home page, select "Overview Page for", choose test1 or test2 from dropdown list Actual results: 2.When there is only one project, user2 is able to set home page to project test1 overview page 4.user2 couldn't set home page to any project overview page and we could see error "You are not authorized to add to this project", when this error happens, other options are disabled too and user could not change home page preference Expected results: 4.Viewer should be able to set homepage to any project overview page although he has view access Additional info:
I am able to reproduce this, there error is coming from the <select-project> dropdown component in Catalog. It is a form validation error. Probably need a way to bypass this 'canI' form validation in this scenario...investigating.
Right, you might still want to set a project as your homepage that you only have view access to. We don't need the canI check since if you see it in the list at all you have some level of access.
Merged PR https://github.com/openshift/origin-web-console/pull/2759
Checked on OpenShift Web Console: v3.9.0-0.47.0 Project viewer now is able to set home page to any one of project he has view access