oauth 2.0 - does authorization code for gmail oauth2 ever expires -
i trying use gmail smtp using oauth 2.0. have used aspose.dll requesting access token using authorization url. not refresh token when response.so there no way request new access token if previous expired. thought of getting access token every-time app requires . , if authorization code gets expired can not follow approach.
does authorization code gmail oauth2 ever expires??
google's oauth 2.0 provide refresh tokens!!! link here explains various flows , talks apps obtaining both access , optional refresh token scenarios.
authorization code expire! that's oauth protocol dictates. cannot find exact time period quote here google, know facebook), authorization code expires in 10 minutes (see december 5 change in link.).
the refresh token has been made available use cases yours. if authorization code persist, difference remain between refresh token , authorization code.
i'd suggest documentation of aspose libraries using.
ps - authorization code/access tokens/refresh tokens issued central google authorization server! so, we're talking google's authorization code which, said, expire.
good luck!
edit - adding more info you
authorization code generated authorization server. authorization code must expire shortly after issued mitigate risk of leaks. maximum authorization code lifetime of 10 minutes recommended. client must not use authorization code more once. if authorization code used more once, authorization server must deny request , should revoke (when possible) tokens issued based on authorization code. authorization code bound client identifier , redirection uri.
source - http://tools.ietf.org/html/draft-ietf-oauth-v2-31
section - 4.1.2
Comments
Post a Comment