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.

Sign up for GitHub

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

Jump to bottom

Add enabled status of api key and token services to security feature set #38535

Closed
jaymode opened this issue Feb 6, 2019 · 1 comment · Fixed by #38687
Closed

Add enabled status of api key and token services to security feature set #38535

jaymode opened this issue Feb 6, 2019 · 1 comment · Fixed by #38687
Assignees
@bizybot
Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)

Comments

@jaymode
Copy link
Member

jaymode commented Feb 6, 2019

As other applications start to build features against the OAuth2 tokens and the API Keys, we should offer a way for the application to determine if these services are enabled. We already have the feature set api, which provides an easy way to expose whether these services are enabled or not.
@jaymode jaymode added >enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) labels Feb 6, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@bizybot bizybot mentioned this issue Feb 11, 2019
Merged
bizybot added a commit that referenced this issue Feb 14, 2019
@bizybot
Add enabled status for token and api key service (#38687)
d227f8e 
Right now there is no way to determine whether the
token service or API key service is enabled or not.
This commit adds support for the enabled status of
token and API key service to the security feature set
usage API `/_xpack/usage`.

Closes #38535
bizybot added a commit to bizybot/elasticsearch that referenced this issue Feb 14, 2019
@bizybot
Add enabled status for token and api key service (elastic#38687)
b482108 
Right now there is no way to determine whether the
token service or API key service is enabled or not.
This commit adds support for the enabled status of
token and API key service to the security feature set
usage API `/_xpack/usage`.

Closes elastic#38535
@bizybot bizybot mentioned this issue Feb 14, 2019
Merged
bizybot added a commit that referenced this issue Feb 14, 2019
@bizybot
Add enabled status for token and api key service (#38687) (#38882)
335cf91 
Right now there is no way to determine whether the
token service or API key service is enabled or not.
This commit adds support for the enabled status of
token and API key service to the security feature set
usage API `/_xpack/usage`.

Closes #38535
bizybot pushed a commit to bizybot/elasticsearch that referenced this issue Feb 14, 2019
Enable BWC tests after backporting token, api key service status change
e5ed8df 
Enable BWC tests after backporting token, api key service status change.
Addressed TODO to update the version to 7.1.0.

Closes elastic#38535
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bizybot bizybot

Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add enabled status for token and api key service bizybot/elasticsearch
3 participants
@bizybot @jaymode @elasticmachine