Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cut a new release #149

Merged
merged 30 commits into from
Jul 17, 2020
Merged

Cut a new release #149

merged 30 commits into from
Jul 17, 2020

Conversation

mjcheetham and others added 30 commits June 11, 2020 15:45
In order to allow a user that requires SAML SSO to be manually enabled
on their newly generated PATs to access org repos, we must store the PAT
as soon as we generate it. This then allows the user the ability to
visit the web UI, enable SSO, and then repeat their Git operation using
the _same PAT_.

Workaround for issue: #133
github: store the PAT on 'get' request for SAML SSO
Add a document outlining the architecture of GCM Core.
Add Architecture overview document to help developers
Add host provider specification
Add SVG version of GCM logo
…vier for an arbitrary host, i.e. a Bitbucket Server host

Allow HTTP as well as HTTPS for Bitbucket Server hosts

TODO test more complex URLs e.g. https://my.company.com/bitbucket
…. Save with and without usernames since BbS doesn't generally include them in its Git URLs
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@github.com>
A fix for a typo that I noticed in the FAQ 🙂
Use the /organizations authority for MSA accounts with Azure
DevOps/Repos. This is because we're using MSA pass-through, an internal
Microsoft mechanism to support both MSA and 'work' (AAD) accounts with
the same auth stacks.

You should be able to use /common, but this doesn't work. At the same
time we're using ADAL Obj-C on macOS rather than MSAL.NET like we do on
Windows, and ADAL speaks to the "v1" AAD endpoints, which don't know the
/organizations tenant :(

For macOS we need to fudge the authority _back_ to /common for MSA
accounts.
Fix Azure Repos sign-in with Microsoft Accounts
Use the final OAuth2 device authorization endpoint URI.
Enable the device code authorization grant flow for GitHub.
Enable OAuth device authorisation grant support for GitHub
@mjcheetham mjcheetham merged commit 819e6bc into release Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants