Repository navigation
Atru/hcp ibmid login ipe 1573 - #3478
Open
trujillo-adam wants to merge 13 commits into
Open
trujillo-adam wants to merge 13 commits into
trujillo-adam wants to merge 13 commits into
Conversation
Contributor
Vercel Previews Deployed
|
Contributor
Broken Link CheckerThis PR contains broken links, but won't be blocked. Use this report to improve content quality: Quick Actions
Need Help?
Internal LinksExternal LinksSummary
Errors per inputErrors in content/hcp-docs/content/docs/hcp/create-account.mdx
Errors in content/hcp-docs/content/docs/hcp/iam/mfa.mdx
Errors in content/hcp-docs/content/docs/hcp/iam/sso/setup/saml.mdx
Redirects per inputRedirects in content/hcp-docs/content/docs/hcp/create-account.mdx
Redirects in content/hcp-docs/content/docs/hcp/iam/mfa.mdx
Redirects in content/hcp-docs/content/docs/hcp/iam/sso/setup/saml.mdx
|
robin-norwood
previously approved these changes
Sep 21, 2026
robin-norwood
left a comment
robin-norwood
left a comment
Contributor
There was a problem hiding this comment.
lgtm with some suggestions.
|
|
||
| At the HCP login screen, click the **GitHub** sign-in option. HCP automatically recognizes the matching email and adds GitHub as a sign-in method for your existing account. Your organization memberships, roles, and resource access are unchanged. | ||
|
|
||
| ### Sign in with a different email address |
Contributor
There was a problem hiding this comment.
This heading matches the one above on line 73. I think the default for anchor links is to go to the first heading, but we should probably avoid this anyway.
Contributor
Author
There was a problem hiding this comment.
Good callout, but I think we're OK in this case because we are only, and should only, be linking to the parallel topic in the IBMid section.
Co-authored-by: Robin Norwood <robin.norwood@gmail.com> Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
segmentation-violation
approved these changes
Oct 9, 2026
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
mattschouten
previously approved these changes
Oct 12, 2026
mattschouten
left a comment
mattschouten
left a comment
Contributor
There was a problem hiding this comment.
A few suggested changes, and a rendering issue on saml.mdx. Approving so you can merge if needed though.
| ## Enable SAML SSO for HCP | ||
|
|
||
| After your domain is verified, you can set up SAML SSO. | ||
| <!-- TODO: Uncomment when SAML changes are ready to publish: |
Contributor
There was a problem hiding this comment.
Noting TODOs in this file, just in case.
| | Email and password | MFA is managed in HCP. | Refer to [Enable MFA](#enable-mfa). | | ||
|
|
||
| With MFA, you will need a password (credential), and an authenticator application downloaded to your phone. HCP offers one method of MFA called **one-time password (OTP)**. An OTP is a sequence of numbers that are generated by an authenticator application. If you lose your device, you can use the recovery code provided during the setup process. Make sure to record the recovery code and save it to a secure location. | ||
| Changes to MFA affect your access to HashiCorp Developer, Discuss, Events, and the Certification Portal, because the same account is used to access those sites. |
Contributor
There was a problem hiding this comment.
I did see an earlier comment about Discuss - not sure if that's relevant here.
|  | ||
|
|
||
| To mitigate this issue, try re-generating a new OTP. If you misplaced your device or unable to access your device, or need to sign in without one, use the recovery code that you securely saved to sign back into [the HCP Portal](https://portal.cloud.hashicorp.com/). Note that there may be a five-minute time-out period if you did not complete the setup process within the timeframe given to complete the MFA setup process. | ||
| Try generating a new OTP. If you cannot access your device, use the recovery code you saved during setup to sign in. The setup process times out after five minutes; if the timeout expires, restart the setup. |
Contributor
There was a problem hiding this comment.
Should a new paragraph start at "If"? It's not clear to me if "If" starts a new problem to troubleshoot, or if it's a continuation of code verification.
| For more information, refer to [HCP Europe](/hcp/docs/hcp/europe). | ||
| <Warning> | ||
|
|
||
| Email and password sign-in is deprecated and will be removed from HCP on 31 January 2027. Before that date, add IBMid or GitHub as a sign-in method for your account. |
Contributor
There was a problem hiding this comment.
When the above Warning is uncommented, this paragraph can be removed, right?
| ## Account Settings | ||
| ## Requirements | ||
|
|
||
| Only users who signed up for HCP with their email and password or with GitHub can [remove their accounts](#remove-your-account) in the HCP UI. SSO users, including SCIM-provisioned users, cannot remove their own accounts from the portal. If you authenticate using SSO, contact your organization administrator so that they can de-provision your account through your identity provider. |
Contributor
There was a problem hiding this comment.
Suggested change
| Only users who signed up for HCP with their email and password or with GitHub can [remove their accounts](#remove-your-account) in the HCP UI. SSO users, including SCIM-provisioned users, cannot remove their own accounts from the portal. If you authenticate using SSO, contact your organization administrator so that they can de-provision your account through your identity provider. | |
| Only users who signed up for HCP with their email and password or with GitHub can [remove their accounts](#remove-your-account) in the HCP UI. SSO users, including SCIM-provisioned users, cannot remove their own accounts using the portal. If you authenticate using SSO, contact your organization administrator so that they can de-provision your account through your identity provider. |
|
|
||
| Only users who signed up for HCP with their email and password or with GitHub can [remove their accounts](#remove-your-account) in the HCP UI. SSO users, including SCIM-provisioned users, cannot remove their own accounts from the portal. If you authenticate using SSO, contact your organization administrator so that they can de-provision your account through your identity provider. | ||
|
|
||
| If your organization uses SSO, HashiCorp recommends maintaining at least two non-SSO users with administrative access. If all non-SSO administrative users are removed and SSO is later disabled, no local user may have sufficient permissions to administer the organization. Refer to [Single sign-on (SSO) overview](/hcp/docs/hcp/iam/sso) for more information. |
Contributor
There was a problem hiding this comment.
Suggested change
| If your organization uses SSO, HashiCorp recommends maintaining at least two non-SSO users with administrative access. If all non-SSO administrative users are removed and SSO is later disabled, no local user may have sufficient permissions to administer the organization. Refer to [Single sign-on (SSO) overview](/hcp/docs/hcp/iam/sso) for more information. | |
| If your organization uses SSO, HashiCorp recommends maintaining at least two non-SSO users with administrative access. If all non-SSO administrative users are removed and SSO is later disabled, no local user will have sufficient permissions to administer the organization. Refer to [Single sign-on (SSO) overview](/hcp/docs/hcp/iam/sso) for more information. |
| <Warning> | ||
| If your organization uses SSO, HashiCorp recommends maintaining at least one non-SSO user with administrative access. If all non-SSO administrative users are removed and SSO is later disabled, no local user may have sufficient permissions to administer the organization. | ||
| </Warning> | ||
| Before removing your account, HCP performs an automated pre-flight check and blocks removal if you are the owner of one or more HCP organizations. You must resolve all ownership dependencies before your account can be removed. |
Contributor
There was a problem hiding this comment.
Suggested change
| Before removing your account, HCP performs an automated pre-flight check and blocks removal if you are the owner of one or more HCP organizations. You must resolve all ownership dependencies before your account can be removed. | |
| Before removing your account, HCP performs an automated check and blocks removal if you are the owner of one or more HCP organizations. You must resolve all ownership dependencies before your account can be removed. |
|
|
||
| - [Multi-factor authentication](/hcp/docs/hcp/iam/mfa) | ||
| - [Single sign-on (SSO) overview](/hcp/docs/hcp/iam/sso) | ||
| - [Invite users to an organization](/hcp/docs/hcp/admin/users#invite-users) |
Contributor
There was a problem hiding this comment.
Suggested change
| - [Invite users to an organization](/hcp/docs/hcp/admin/users#invite-users) | |
| - [Invite users to an organization](/hcp/docs/hcp/iam/users#invite-users) |
| ## Enable SAML SSO for HCP | ||
|
|
||
| After your domain is verified, you can set up SAML SSO. | ||
| <!-- TODO: Uncomment when SAML changes are ready to publish: |
Contributor
There was a problem hiding this comment.
This file doesn't render in the Vercel preview. When I try locally, it throws an error that seems to point to one of the <!-- TODO comments.
If it all renders okay for you, no big deal. Otherwise there may be something goofy going on with the TODOs.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the HCP docs to include information about logging in with IBMid and GitHub. It also fixes several style guide violations, but a comprehensive style guide review is out of scope.