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] Api key format doesn't match current UI #235

Closed
Dig-Doug opened this issue Jul 7, 2024 · 1 comment · Fixed by #238
Closed

[DOCS] Api key format doesn't match current UI #235

Dig-Doug opened this issue Jul 7, 2024 · 1 comment · Fixed by #238
Labels
documentation Improvements or additions to documentation

Comments

@Dig-Doug
Copy link

Dig-Doug commented Jul 7, 2024

The ApiKey credential currently asks for a key id and an api key. However, in the elasticsearch cloud UI, API keys don't provide these components separately. Instead, they provide base64(keyid + ":" + key) as one string. Since you also give API keys a name, my initial thought was to provide the api key name as the id and then the base64 key as the value.

Either the rust client should be updated to take this format or the docs should be updated to make it clear how to get these values.

@Dig-Doug Dig-Doug added the documentation Improvements or additions to documentation label Jul 7, 2024
@swallez
Copy link
Member

swallez commented Aug 26, 2024

In PR #238 we added a new EncodedApi credential that takes a single string so that both representations of API keys can be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants