Getting asked to sign-in using SSO even after leaving the organisation #176067
Replies: 6 comments 6 replies
-
|
This happens because your GitHub account still has an active SSO link to your old organization. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
I tried everything mentioned in the comments above but the issue still persists. |
Beta Was this translation helpful? Give feedback.
-
|
I am running into a similar issue where I am the owner of an Enterprise that is setup with SSO and in order to manage the enterprise to remove myself I would need to have access to SSO system (Okta) which I no longer have. I have already successfully removed myself from the organization, but cannot do anything to remove the enterprise from my account. How can I rectify this? |
Beta Was this translation helpful? Give feedback.
-
|
Had the same problem. I've found out that I still had the org added through |
Beta Was this translation helpful? Give feedback.
-
|
The Fix Go to your GitHub Settings. Click Organizations (in the left sidebar). Find your previous employer and click Leave. The Reason Your account is still listed as a "member," which forces GitHub to check for SSO. Leaving the organization downgrades you to a "public user," allowing you to view the public repos without logging in to Okta. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi folks,
I was a part of an organisation before and have forked a few public repositories from there, I had the Okta SSO enabled so whenever I used to open a PR or commit in those repositories, I needed to authenticate using SSO.
Now I have left the organisation but when I open the pull requests tab for any of those public repositories, I am still being asked to authenticate using SSO, which I cannot do because I do not have any access to my previous organisation's SSO tool. Funny enough, I can copy the link and open the link in an incognito window properly where my GitHub account is not logged in so the issue is definitely connected somewhere with my account.
My question is, how do I resolve this? I am no longer a part of the organisation and I do not have any links with it now and yet somewhere, some connections seems to be active.
For example, I can open yugabyte/debezium#184 without logging to my account, but when I am logged in, I am being asked to authenticate. What could I be missing here?
Beta Was this translation helpful? Give feedback.
All reactions