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

Single sign-on update #234

Merged
merged 2 commits into from
Jul 26, 2019
Merged

Single sign-on update #234

merged 2 commits into from
Jul 26, 2019

Conversation

jonathanglassman
Copy link
Contributor

What

The single sign-on function previously only worked for people in GDS with a GDS email address. It now works for everyone with a Google or Microsoft account. This updated content reflects this.

How to review

Describe the steps required to test the changes.

  1. Preview the content locally (see README) and check that it renders as expected.
  2. Manually check that any removed or renamed anchor tags are not in use (linkchecker doesn't do this).
  3. Check it completes https://www.pivotaltracker.com/story/show/167345982

Who can review

Describe who can review the changes. Or more importantly, list the people
that can't review, because they worked on it.


The email attached to your GOV.UK PaaS account must be the same as the email attached to your Google or Microsoft account.
You must have either a [Google](https://myaccount.google.com/intro) or [Microsoft](https://account.microsoft.com/account) email address to use single sign-on. The email address must be the same as the one you use to sign into your GOV.UK PaaS account.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The email address must be the same as the one you use to sign into your GOV.UK PaaS account.

Is this actually true? @tlwr?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This used to be the case for Google

For Microsoft I do not think it is the case

I assume Google will no longer be the case after we enable it for everyone

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's my understanding too. A bit confusing to have people use accounts with different emails, but I think it will be possible.

Maybe it's better to have this sentence in the docs, even if it's not technically true?

@jonathanglassman jonathanglassman merged commit 921cf3e into master Jul 26, 2019
@jonathanglassman jonathanglassman deleted the sso-update branch July 26, 2019 07:34
tlwr pushed a commit that referenced this pull request Aug 1, 2019
In this pull request #236
we added new documentation about the V3 API, but this PR also included
some single sign-on content (from #234) that has since been overwritten

This commit recommits the content which we care about.

Co-authored-by: Jon <[email protected]>
Co-authored-by: Toby <[email protected]>

Rename ssh.md to ssh.erb & add warning text v3 ssh
tlwr pushed a commit that referenced this pull request Aug 1, 2019
In this pull request #236
we added new documentation about the V3 API, but this PR also included
some single sign-on content (from #234) that has since been overwritten

This commit recommits the content which we care about.

Co-authored-by: Jon <[email protected]>
Co-authored-by: Toby <[email protected]>
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.

3 participants