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 with Pantheon Doc Update #9239

Open
titomarifrancis-pantheon opened this issue Sep 30, 2024 · 1 comment
Open

Single Sign-on with Pantheon Doc Update #9239

titomarifrancis-pantheon opened this issue Sep 30, 2024 · 1 comment
Assignees
Labels
Topic: Dashboard Type: Fix Content Issue or PR to resolve incorrect information in the docs

Comments

@titomarifrancis-pantheon
Copy link
Contributor

Re: Single Sign-on with Pantheon

Priority: High

Issue Description:

The line that says:
The user_id attribute must be configured to be sent manually. If this value is not already present, it should be set to match the email attribute

contains the word "must" which means it's imperative that this step be performed as well, rather than be an optional additional step of the process.

This is pointed out by a customer, and hereby requested for the documentation to be updated

Suggested Resolution

Move this line:
The user_id attribute must be configured to be sent manually. If this value is not already present, it should be set to match the email attribute.

from Additional configuration details section to another enumerated item after Add an Attribute Statement

@stevector stevector added the Type: Fix Content Issue or PR to resolve incorrect information in the docs label Oct 2, 2024
@stevector
Copy link
Contributor

@jazzsequence can you take a pass at updating this doc? We'll need review from someone in technical solutions or a similar area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Topic: Dashboard Type: Fix Content Issue or PR to resolve incorrect information in the docs
Projects
None yet
Development

No branches or pull requests

3 participants