Allow access_token_ttl to be passed as callback #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some scenarios we might have some specific business logic where TTL depends on the client or other similar conditions. To support client specific TTL allow `access_token_ttl` to be passed as callback so that we can call our own conditions on what the lifespan of the token should be.
vskrupskis
force-pushed
the
valters/access_token_ttl_as_callback
branch
from
60a74a1
to
7024ff6
Compare
|
Looks good! Merging, will be on the way to CPAN shortly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some scenarios we might have some specific business logic where TTL
depends on the client or other similar conditions.
To support client specific TTL allow
access_token_ttlto be passed ascallback so that we can call our own conditions on what the lifespan of
the token should be.