Closed kelsey-dirks closed 2 weeks ago
Hey @kmosher Checking to see if you have any updates to when you could address this content bug?
Just confirming that these docs are still incorrect. There's also no longer a SAML SSO item under the Settings tab.
@meagancojocar Would it be possible to have someone familiar with configuring each of these providers run through these pages to make sure they're all correct? I suspect there are lots of little outdated things like this that'll likely trip up users.
PR has been created to make updates to the documentation. Waiting for approval and merging
What happened?
Our docs say, "For HTTP HEADER, you will use a token from the Pulumi Cloud as the authorization bearer token. To generate a token, navigate to your org in the Pulumi Cloud, click on the Settings tab, and then click SAML SSO. Scroll down to the SCIM section and generate a new token if you have never generated one for your org, or regenerate it if you have already done so in the past."
However, the Pulumi Cloud doesn't generate a token. It instead tells the user to contact support. The doc will need to be updated to reflect our new process.
Expected Behavior
NA
Steps to reproduce
The doc that needs updating: https://www.pulumi.com/docs/guides/scim/okta/#configuring-the-scim-connector
Output of
pulumi about
NA
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).