Skip to content
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

Merged
merged 3 commits into from
Nov 15, 2019
Merged

[DOCS] Edits the get tokens API #45312

merged 3 commits into from
Nov 15, 2019

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Aug 7, 2019

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.

@lcawl lcawl added >docs General docs changes :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) v8.0.0 v7.4.0 labels Aug 7, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs

@elasticmachine
Copy link
Collaborator

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`::
Copy link
Member

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

Copy link
Contributor Author

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.

@colings86 colings86 added v7.5.0 and removed v7.4.0 labels Aug 30, 2019
@lcawl lcawl marked this pull request as ready for review September 5, 2019 15:53
@jimczi jimczi added v7.6.0 and removed v7.5.0 labels Nov 12, 2019
@lcawl lcawl merged commit 2234090 into elastic:master Nov 15, 2019
@lcawl lcawl deleted the get-tokens branch November 15, 2019 18:50
lcawl added a commit that referenced this pull request Nov 15, 2019
@lcawl lcawl added the v7.5.0 label Nov 15, 2019
lcawl added a commit that referenced this pull request Nov 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) v7.5.0 v7.6.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants