This could be the possible scenario happens with wso2 AM.
1. If the token is generated thru UI for the first time, Refresh token may miss in the next token request with grant type as ‘password’.
2. Once that token is revoke with the curl request we were able to get the refresh token.
Sample curl request we used:
curl -k -d "token=<ACCESS_TOKEN_TO_BE_REVOKED>" -H "Authorization: Basic Base64Encoded(Consumer key:consumer secret)" http://localhost:8280/revoke
3. Even the "RefreshTokenValidityPeriod" expires server didn't generate the refresh token.We found that we need to investigate further on this point.
Following the configuration we found in the "identity.xml"
<AccessTokenDefaultValidityPeriod>3600</AccessTokenDefaultValidityPeriod>
<RefreshTokenValidityPeriod>84600</RefreshTokenValidityPeriod>
<RenewRefreshTokenForRefreshGrant>true</RenewRefreshTokenForRefreshGrant>
2. Once that token is revoke with the curl request we were able to get the refresh token.
Sample curl request we used:
curl -k -d "token=<ACCESS_TOKEN_TO_BE_REVOKED>" -H "Authorization: Basic Base64Encoded(Consumer key:consumer secret)" http://localhost:8280/revoke
3. Even the "RefreshTokenValidityPeriod" expires server didn't generate the refresh token.We found that we need to investigate further on this point.
Following the configuration we found in the "identity.xml"
<AccessTokenDefaultValidityPeriod>3600</AccessTokenDefaultValidityPeriod>
<RefreshTokenValidityPeriod>84600</RefreshTokenValidityPeriod>
<RenewRefreshTokenForRefreshGrant>true</RenewRefreshTokenForRefreshGrant>
No comments:
Post a Comment