We use membership in BCDevOps org in GitHub to control user access to the Openshift 4 Console. Access to the namespaces is set up within Openshift itself by the namespace admins. User authentication when accessing the Openshift 4 Console is handled by the KeyCloak SSO service.
When you change your GitHub ID, it messes up with your account record in both systems - KeyCloak SSO and Openshift - that store a cache your GitHub ID. To resolve the access issues, follow the steps below.
Step 1: Ask your PO or Tech Lead to remove your old user from the namespaces in Openshift where you had access before.
Step 3: To force the refresh of your account record, contact the Platform Services Team at PlatformServicesTeam@gov.bc.ca and request the following:
delete your old GitHub ID from Kq56c126, DevHub and GitHub realms in KeyCloak SSO
delete your user in Openshift 4 Silver cluster
remove your old GitHub ID from BCDevOps and bcgov orgs
Step 4: After this ask your PO or Tech Lead to add your new GitHub ID to BCDevOps and bcgov orgs using the Just Ask! tool and then add your user to the namespaces that you need to have access to.
After these steps, clear your browser cache , and log into the Openshift 4 Console. You should see the list of projects to which you've been given access to in Step 4.
We use membership in
BCDevOpsorg in GitHub to control user access to the Openshift 4 Console. Access to the namespaces is set up within Openshift itself by the namespace admins. User authentication when accessing the Openshift 4 Console is handled by theKeyCloak SSOservice.When you change your GitHub ID, it messes up with your account record in both systems - KeyCloak SSO and Openshift - that store a cache your GitHub ID. To resolve the access issues, follow the steps below.
Step 1: Ask your PO or Tech Lead to remove your old user from the namespaces in Openshift where you had access before.
Step 3: To force the refresh of your account record, contact the Platform Services Team at PlatformServicesTeam@gov.bc.ca and request the following:
Kq56c126,DevHubandGitHubrealms in KeyCloak SSOStep 4: After this ask your PO or Tech Lead to add your new GitHub ID to
BCDevOpsandbcgovorgs using the Just Ask! tool and then add your user to the namespaces that you need to have access to.After these steps, clear your browser cache , and log into the Openshift 4 Console. You should see the list of projects to which you've been given access to in Step 4.