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

Add API key settings documentation (#38490) #38499

Merged
merged 1 commit into from
Feb 6, 2019

Conversation

bizybot
Copy link
Contributor

@bizybot bizybot commented Feb 6, 2019

This commit adds missing
API key service settings documentation.

This commit adds missing
API key service settings documentation.
@bizybot bizybot added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) backport labels Feb 6, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@jasontedor jasontedor changed the base branch from 6.x to 6.7 February 6, 2019 13:06
@jasontedor jasontedor reopened this Feb 6, 2019
@bizybot
Copy link
Contributor Author

bizybot commented Feb 6, 2019

@elasticmachine run elasticsearch-ci/2

1 similar comment
@bizybot
Copy link
Contributor Author

bizybot commented Feb 6, 2019

@elasticmachine run elasticsearch-ci/2

@bizybot bizybot merged commit eccde9c into elastic:6.7 Feb 6, 2019
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Feb 8, 2019
* 6.7:
  Fix build on Fips (elastic#38546)
  ML: update set_upgrade_mode, add logging (elastic#38372) (elastic#38539)
  Update 'removal of types' docs to reflect the new plan. (elastic#38548)
  Make the 'get templates' types deprecation message consistent. (elastic#38532)
  Add API key settings documentation (elastic#38490) (elastic#38499)
  Mute testExpiredApiKeysDeletedAfter1Week in 6.7 (elastic#38528)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants