My requirement is that I need to create a refresh_token with no expiry and use the same token to regenerate new access_token when they expire. I referred the documentation and found that if we pass refreshTokenLifetime in the custom middleware as null it will create a refresh_token with no Expiry. But A new refresh_token is generated for every grant_type is refresh-token. According to the IETF Document , it is optional to generate a new refresh_token when the grant-type is refresh-token. Is there any way to make the refresh_token generation as an optional when the refreshTokenLifeTime is null in the custom middleware.
I created a middleware using express as shown in Documentation for Node OAuth2 Server.
My requirement is that I need to create a refresh_token with no expiry and use the same token to regenerate new access_token when they expire. I referred the documentation and found that if we pass refreshTokenLifetime in the custom middleware as null it will create a refresh_token with no Expiry. But A new refresh_token is generated for every grant_type is refresh-token. According to the IETF Document , it is optional to generate a new refresh_token when the grant-type is refresh-token. Is there any way to make the refresh_token generation as an optional when the refreshTokenLifeTime is null in the custom middleware.
I created a middleware using express as shown in Documentation for Node OAuth2 Server.
My code is as follows
Node Version I am using is 4.2.4