-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
[DOCS] Edits the get tokens API #45312
Conversation
Pinging @elastic/es-docs |
Pinging @elastic/es-security |
for an access token and (possibly) a refresh token. The request needs to be made | ||
by an authenticated user but happens _on behalf_ of another authenticated user | ||
(the one whose credentials are passed as request parameters). This grant type is | ||
not suitable or designed for the self-service user creation of tokens. | ||
|
||
`password`:: |
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.
I'm not sure what is the best way to convey that these are Required
but only when the appropriate grant is selected with the (Optional/Required, <parameter_type> template. I can make arguments both for
Optional, as in it is optional depending on the grant type parameter selected and for
Required` since these are required parameters for the relevant grant type. I'll defer to @lcawl when she is back from holidays to make the decision
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.
I chatted with the other folks working on this new API template and we propose using "Optional*" and clarify that it's required in XXX situation. I've made that change in this PR.
Related to #36946
This PR adds a "Prerequisites" section to the get tokens API reference. It also moves descriptions of the grant types into the appropriate parameter definitions.