JaradD.23099 (CDK) asked a question.
I am trying to get a new id token from the refresh token provided at initial login. The initial login was done with PKCE since we have a public native app.
The examples okta provides looks to be fore non-PKCE Authorization Code flow because it has a basic auth Authorization header
https://developer.okta.com/docs/guides/refresh-tokens/use-refresh-token/
I tried leaving that off and then providing the client_id header and I get:
{
"errorCode": "invalid_client",
"errorSummary": "Invalid value for 'client_id' parameter.",
"errorLink": "invalid_client",
"errorId": "oaeY1AplM70QsqFrH9nO_ku3Q",
"errorCauses": []
}
headers:
Content-Type: application/x-www-form-urlencoded
grant_type: refresh_token
redirect_uri: http://127.0.0.1:5127/auth
refresh_token: {refresh_token}
client_id: {client_id}
This is possible. You are right though it is not documented or shared any where by Okta.
POST https://${yourOktaDomain}/oauth2/default/v1/token
headers:
content-type:application/x-www-form-urlencoded
body:
client_id=0oa1….4h4x7
grant_type=refresh_token
refresh_token=8vAnXd9…….LiQlIB8R4X5No
That combination of headers and body will allow you to get new ID Tokens and Access Tokens from the Refresh Token.