Skip to content

Linked the TFE table to help with manual configuration #771

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Linked the TFE table to help with manual configuration #771

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions website/docs/cloud-docs/users-teams-organizations/single-sign-on/okta.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,9 @@ For more information on the listed features, visit the [Okta Glossary](https://h

For information on configuring automated team mapping using Okta group membership, please see the [Team Mapping Configuration (Okta)](#team-mapping-configuration-okta-) section below.

Creation of an Application on Okta side requires elevated privileges. For that reason customers sometimes create a workflow to provision it, leaving the end user with a need to configure the actual settings.
Copy link
Contributor

Choose a reason for hiding this comment

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

Because this is a very particular scenario you are describing about setting up an Okta feature, rather than an HCP Terraform feature, it feels like it might be a better fit for a support article, rather than an additional to our documentation. In general, we want to try to avoid describing how other products work in our documentation as much as possible. Let me know what you think though! Happy to have a conversation about this if you disagree!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I understand. Let me rephrase a little bit then.
Configuration using Terraform Cloud application from Okta side is flawless and requires very few steps.
Some customers don't want to grant this level of access and they use a separate workflow to create a generic app in Okta. When you look at the table from step 4, Single sign on URL on our side is ACS Consumer in Okta. Customers tend to paste a wrong value in Okta because our config shows Single sign on URL as well.
To sum it up, they do not what's in the table, but Single sign on from HCP -> Single sign on in Okta.
This already exists in TFE docs, probably for exactly that reason. I can do the article if you still think it's the best route. Just wanted to make sure the why is clear.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for the extra context, I really appreciate it! I do still think this would be better presented in a support article because it is such a particular use case and workflow that has more to do with Okta than on our own products. Thanks for looping me in though!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Cool, I will close this after creating a KB.

In such a case, the [table](https://developer.hashicorp.com/terraform/enterprise/saml/idp-configuration/okta#configure-a-new-okta-saml-application) from step number four might aid with manually copying and pasting the various links.
|
## Configuration (HCP Terraform)

Be sure to copy the metadata URL (from the final step of configuring Okta) before proceeding with the following steps.
Expand Down