-
Notifications
You must be signed in to change notification settings - Fork 33
[DO NOT MERGE] Updated TV and added Connected Accounts doc #259
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
Conversation
de98a63 to
c3e00fa
Compare
main/docs/secure/tokens/token-vault/connected-accounts-for-token-vault.mdx
Outdated
Show resolved
Hide resolved
| <td><strong>Purpose</strong></td> | ||
| <td>Enable the connection for Authentication, Connected Accounts for Token Vault, or both. To learn more, read [User authentication vs Connected Accounts](/docs/secure/tokens/connected-accounts-for-token-vault#user-authentication-vs-connected-accounts).</td> | ||
| </tr> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enable the connection for Authentication, Connected Accounts for Token Vault, or both
This article is for authentication only, right? Why are we saying that tenants can enable the "Connected Accounts for Token Vault" option?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@siacomuzzi the intent was to capture all the purpose settings shown to users in the UI here, and if users want to learn more about connected accounts, they can click on the link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, but is this a generic article about how to configure a connection, or about how to configure a connection for authentication only?
If the latter, we should say that the requirement is to have the Purpose set to "Authentication" or "Both".
But, if this article is a generic article about connection provisioning, feel free to ignore my comment. It confused me that it’s under the “/authenticate/” path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you have a point that this doc + the docs under /authenticate are technically for login. unfortunately, there isn't a better place atm to document all the purpose setting on the main docs. eventually, the docs team will need to come up with a strategy on either updating the connection docs on Marketplace or migrating those connection docs back to the main docs, but for GA, hopefully this is an okay workaround :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@siacomuzzi the actual feature name is "Connected Accounts for Token Vault." i synced with @cristiandouce and understand that the copy will reflect this in a future milestone:


By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description
References
Testing
Checklist