django - It is normal for an OAuth2 implementation to create a new access token every authentication? -
i'm using oauth 2.0 implementation (django-ouath-toolkit) , noticed every time user request access token new registry in database. normal behaviour? should not recycled/replaced application , user every authentication request? if user logs in 5 times in row, 5 returned access tokens stored , valid until expires. if relevant, i'm using password
grant type , public client type.
thank all.
yes, common practice: new access-token created on each authentication request.
it is, however, uncommon user log in 5 times in row.
Comments
Post a Comment