Cannot access Github Issues/ PRs from a public Microsoft owned repository.

[sandrohanea]

Select Topic Area

Product Feedback

Body

Hello,

I am part of https://github.com/microsoft organization, and I am logged on github from 2 devices (one is Microsoft owned, and the other one not).

On the one owned by Microsoft, everything is working as expected (as I am logged in with @microsoft account in my edge browser).

On the other laptop, I am logged in with my personal account in the edge browser and whenever I tried to access public issues or PRs, it redirects me to this page:

If I tried to login, it will fail as my personal account cannot be used for Open Source Enterprise Cloud Access (1ES)

Expected behavior:

I expect to see the public issues / PRs even if not authenticated with my @microsoft account.

Options:

1. be able to access them directly and require another authentication only if doing something that requires more than public access (e.g. Approve some PR)

2. Besides, "continue" in Single sign-on to Microsoft Open Source to have an option to "Continue as public".

Workaround:

I can open any issue in another browser where I'm not logged or just open it in Incognito and I can see them, but it's not really convenient.

[theficus]

I'm piling on to this in the hope that it gets some more visibility. I've also seen this mentioned in #9045 and #13088 but nothing has had any response as of yet.

This issue makes GitHub mostly unusable for me in any personal capacity. Even if I'm not doing things in a work capacity, I often have a need to view code, PRs, or issues in otherwise public Microsoft repositories. The SSO device management requirements make it so that I actually have fewer privileges against a public Microsoft repository than an unauthenticated user! That feels deeply wrong to me.

There really needs to be a way to bypass this requirement for performing non-privileged operations against public repositories. I like the suggestion 2 as a way of being able to tell GitHub "just treat me like any other user out there rather than someone tied to an organization". As things are today, it's just not viable for me to have a single account on GitHub for personal and work things because of these restrictions.

[bryan-bar]

I am part of an organization and experiencing the same issue when trying to access any of the public repos on personal devices.
I do not want to use single sign-on as I do want to see private repos on personal devices.

I am unable to do the following without my organizations single-sign on:

• access organizations github page to see list of public repos
• access public pull requests
• switch branches on the organization's public repo
• see contributions made to organization's public repo on my account page

I am still able to access the repo by searching for it, or with the link, as well as my own forks and branches.

If I am not logged in, I am able to access my organization's page, public repos, switch branches, read PRs, see contributions made to organizations public repos on my account.

[stefanflegg]

I also experience this problem after linking my personal GH account to the MSFT org. Are there any updates to share on this?

There are some other discussions on the same topic:
https://github.com/orgs/community/discussions/9045
https://github.com/orgs/community/discussions/13088

[qiyuangong]

This issue is blocking me from accessing the public repo of the organization on my laptop.

Unfortunately, it's designed to act this way. Found this description in doc https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on#about-saml-sso

IdP authentication is not required for accessing public repositories in certain ways:

Viewing the repository's overview page and file contents on GitHub
Forking the repository
Performing read operations via Git, such as cloning the repository
Authentication is required for other access to public repositories, such as viewing issues, pull requests, projects, and releases.

Note: SAML authentication is not required for outside collaborators. For more information about outside collaborators, see "Roles in an organization."

Any idea of disabling it?

[David-Noble-at-work]

And I’ll add-on: I’m a former MS employee decoupled from MS having taken care to unlink my MS e-mail from my account. What more must I do to completely sever my relationship and join the good people of the open source community?