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 OktaConfiguration object has two APIKey properties
ApiKey
ApiKeyPrefix
These values are used in the APIs to set a Header parameter of apiToken to be the value inside ApiKey.apiToken and ApiKeyPrefix is ignored. The documentation about APIKey authorization says the header shoudl be Authorization and it should be a prefix of SSWS followed by the auth token per https://github.com/okta/okta-powershell-cli/blob/main/openapi3/management.yaml#L16409
Pass the API token as the Authorization header value prefixed with SSWS: `Authorization: SSWS {API Token}`
The test case I am using is attempting is this after digging into the code to find the structure of the ApiKey is this:
The source of this is that setting the ApiKey is not being passed in to the Authorization header
I did find the swapping in terminology between ApiToken and ApiKey to be a bit challenging so it could be that Im misreading what ApiKey and Prefix is, but the yaml appeasr to indicate the terms being used interchangably
The text was updated successfully, but these errors were encountered:
Thanks @laura-rodriguez , I did do that headers one too, but with there being an ApiKey property I figured Id go the extra yard and make that useful too. If that property is for some other ApiKey then be cool to know what its use case is
The OktaConfiguration object has two APIKey properties
These values are used in the APIs to set a Header parameter of apiToken to be the value inside ApiKey.apiToken and ApiKeyPrefix is ignored. The documentation about APIKey authorization says the header shoudl be
Authorization
and it should be a prefix ofSSWS
followed by the auth token per https://github.com/okta/okta-powershell-cli/blob/main/openapi3/management.yaml#L16409The test case I am using is attempting is this after digging into the code to find the structure of the ApiKey is this:
Which returns this
The source of this is that setting the ApiKey is not being passed in to the Authorization header
I did find the swapping in terminology between ApiToken and ApiKey to be a bit challenging so it could be that Im misreading what ApiKey and Prefix is, but the yaml appeasr to indicate the terms being used interchangably
The text was updated successfully, but these errors were encountered: