-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Release OTR mode for application key #29541
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?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,6 +16,18 @@ API keys are unique to your organization. An [API key][1] is required by the Dat | |
|
||
[Application keys][2], in conjunction with your organization's API key, give users access to Datadog's programmatic API. Application keys are associated with the user account that created them and by default have the permissions of the user who created them. | ||
|
||
### One-Time Read Mode | ||
|
||
One-Time Read (OTR) mode is a security feature that limits the visibility of application key secrets to creation time only. When enabled: | ||
|
||
- Application key secrets are only visible once, immediately after creation | ||
- The raw values cannot be retrieved later via the UI or API | ||
- You must securely store the key value when it is first displayed | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we mention the v1 API change here too? |
||
You can enable OTR mode in [Organization Settings][18]. | ||
|
||
**Note**: For organizations created after [DATE TBD], OTR mode is enabled by default and cannot be disabled. | ||
|
||
### Scopes | ||
|
||
To better protect and secure your applications, you can specify authorization scopes for your application keys to define more granular permissions and minimize the access that applications have to your Datadog data. This gives you fine-grained access control over your applications and minimizes security vulnerabilities by limiting extraneous access. For example, an application that only reads dashboards does not need admin rights to manage users or delete any of your organization's data. | ||
|
@@ -142,3 +154,4 @@ Need help? Contact [Datadog support][16]. | |
[15]: /api/latest/service-accounts/ | ||
[16]: /help/ | ||
[17]: /account_management/org_settings/service_accounts/ | ||
[18]: https://app.datadoghq.com/organization-settings/ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we link directly to the application keys page?
|
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.
Do we need to mention what behavior child-orgs of orgs in otr mode could have?