You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API Key that the Credential Provider is expecting is actually a base 64 encoded JSON document that contains the "endpoint" and the "api_key", with the latter being a JWT. Both of these are returned separately in the RefreshApiKeySuccess structure as Endpoint and ApiKey, respectively, and must be combined by the user into the base64 encoded JSON as previously mentioned.
I can find nowhere in the documentation that this is called out. It is quite different than the JSON that is given for API key creation in the console. Really needs to be changed or documented.
The call to RefreshApiKey should return an apiKey, but It returns a JWT instead.
This makes It impossible to actually rotate keys, as the response that you get back is not a key.
This behavior occurs for both Super User and Fine Grained keys.
The text was updated successfully, but these errors were encountered: