Windows Identity Foundation Extensions Home
HTTP Status 400 Code When Trying to get Refresh Tokens
4/4/2011 9:14:20 PM
User(s) can reproduce this bug
I've attempted to configure a few different ACS v2 subscriptions with no success getting refresh tokens to work. As a work-around we can just get a new authorization code/access token, but that's not ideal and shouldn't be necessary. I'm not entirely sure how to go about troubleshooting this as the ACS v2 is a large black box. I've read over the OAuth2 draft10 spec many times at this point and believe that the data that is going to the ACS is correct. All the other calls are working properly.. I'm able to get authorization codes and access tokens properly, but once the access token expires the request to refresh and get a new access token fails.
Describe the problem that you're having.
Requests to get a new access token using a refresh_token grant_type results in a 400 HTTP status code.
What type of impact does this issue have?
to post a comment.
Please enter a comment.
on 6/8/2011 at 11:52 AM
Does your issue still exist on the latest version of the sample?
on 4/6/2011 at 6:35 AM
Known Issue in "February 2011 Labs Update":-
Requesting an OAuth2 Access token using a Refresh token returns an ACS50000 error
This issue occurs after an OAuth2 access token and refresh token have successfully been issued to a client, and the client uses the refresh token (“grant_type=refresh_token”) to obtain a new access token after the original one expires. Instead of issuing a new access token, the following error messages are returned: "ACS50000: There was an error issuing a token. ACS70000: The provided access grant is invalid, expired or revoked."
These issues have fixes planned for a forthcoming release.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft