Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Apollo
-
Fix Version/s: Apollo
-
Component/s: API
-
Labels:None
-
Environment:
aml-data-tool-2.8.1-oauthprovider-20151110.143237-4.jar
aml-sapi-2.9.0-20151116.101150-265-standalone-no-db-init.war
aml-oauth-provider-1.0.0-20151117.203230-21.war
merchant-api-secure-1.0.0-20151117.203147-21.war
taxonomy-api-secure-1.0.0-20151117.203202-13.war
budget-api-secure-1.0.0-20151111.161638-5.waraml-data-tool-2.8.1-oauthprovider-20151110.143237-4.jar aml-sapi-2.9.0-20151116.101150-265-standalone-no-db-init.war aml-oauth-provider-1.0.0-20151117.203230-21.war merchant-api-secure-1.0.0-20151117.203147-21.war taxonomy-api-secure-1.0.0-20151117.203202-13.war budget-api-secure-1.0.0-20151111.161638-5.war
-
Sprint:Sprint 6
Description
Refresh tokens are getting deleted with expired access token , after generating a new access token with the same client id and client secret .
Steps :
1 . By the help of client id and client secret generate refresh and access token.
2 . After 1 hour the access token will be expired , check in aml-oauth-provider UI .
3. By same client id and client secret generate another refresh and access token .
4 . Log in to the aml-oauth-provider UI .
Expected behavior
Only the expired access token should be deleted .
Actual behavior
Both the refresh token and expired access token are getting deleted.
Note :
Kindly have a look on the screen-shot
