adding obo permission to docs #10332
Conversation
Signed-off-by: Anton Rubin <[email protected]>
AntonEliatra
requested review from
kolchfa-aws,
AMoo-Miki,
natebower,
dlvenable,
epugh and
sumobrian
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
There was a problem hiding this comment.
Thank you, @AntonEliatra! One suggestion. Disregard if this actually references security users that an admin is setting permissions for.
| @@ -95,6 +95,10 @@ While the conversation about the usage of OBO tokens continues, it is critical t | |||
|
|
|||
| For more information, see the [related discussion](https://github.com/opensearch-project/security/issues/2891). | |||
|
|
|||
| ### Permissions | |||
|
|
|||
| In order to execute creation of OBO token the user needs to be assigned `security:obo/create` permission. | |||
There was a problem hiding this comment.
| In order to execute creation of OBO token the user needs to be assigned `security:obo/create` permission. | |
| To create an OBO token, you must have the `security:obo/create` permission. |
Description
adding obo permission to docs
Issues Resolved
Closes #10312
Version
all
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.