-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Aleks/global variable mfa #30616
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
base: master
Are you sure you want to change the base?
Aleks/global variable mfa #30616
Conversation
Update for GV MFA token creation to address recurring questions around supportability of the various MFA providers used by customers. **Note:** If your TOTP token works in Google Authenticator, it will also work with Datadog’s TOTP browser test feature. However, be aware that some MFA providers, such as Duo and Okta, enforce tighter control over how QR codes are interpreted. QR codes generated by these systems might only be valid within their own verification apps (e.g., Duo Mobile or Okta Verify) and may **not** work with general-purpose TOTP authenticators (like Google Authenticator) or Datadog. This is a restriction enforced by the identity provider, not Datadog. To work around this, ensure your QR code or TOTP secret is configured for compatibility with standard TOTP generators.
Updated for brevity **Note:** If your TOTP token works in Google Authenticator, it is likely compatible with Datadog. Some QR codes are restricted to specific verification methods and may not work elsewhere. To ensure compatibility, use a QR code or secret that follows standard TOTP protocols.
📝 Documentation Team Review RequiredThis pull request requires approval from the @DataDog/documentation team before it can be merged. Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes. |
Preview links (active after the
|
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.
Looks good just a small suggestion for wording and clarity !
@@ -243,6 +243,9 @@ To generate and use a TOTP in your tests, create a global variable where you ent | |||
|
|||
{{< img src="synthetics/guide/browser-tests-totp/new-variable-totp.png" alt="Create a MFA token" style="width:100%;" >}} | |||
|
|||
**Note:** If your TOTP token works in Google Authenticator, it is likely compatible with Datadog. |
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.
**Note:** If your TOTP token works in Google Authenticator, it is likely compatible with Datadog. | |
**Note**: If your TOTP token works in Google Authenticator, it is likely compatible with Datadog. |
The colon should be after the bolding
@@ -243,6 +243,9 @@ To generate and use a TOTP in your tests, create a global variable where you ent | |||
|
|||
{{< img src="synthetics/guide/browser-tests-totp/new-variable-totp.png" alt="Create a MFA token" style="width:100%;" >}} | |||
|
|||
**Note:** If your TOTP token works in Google Authenticator, it is likely compatible with Datadog. | |||
Some QR codes are restricted to specific verification methods and may not work elsewhere. To ensure compatibility, use a QR code or secret that follows standard TOTP protocols. |
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.
Some QR codes are restricted to specific verification methods and may not work elsewhere. To ensure compatibility, use a QR code or secret that follows standard TOTP protocols. | |
Some QR codes are limited to specific verification methods and may not work across platforms. To ensure compatibility, use a QR code or secret that follows standard TOTP protocols. |
What does this PR do? What is the motivation?
Update for GV MFA token creation to address recurring questions around supportability of the various MFA providers used by customers.
Updated with:
Note: If your TOTP token works in Google Authenticator, it is likely compatible with Datadog.
Some QR codes are restricted to specific verification methods and may not work elsewhere. To ensure compatibility, use a QR code or secret that follows standard TOTP protocols.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes