Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

98 client specific timeouts #2

Merged
merged 4 commits into from
May 24, 2016
Merged

Conversation

mjsalinger
Copy link
Owner

No description provided.

Michael Salinger added 4 commits January 20, 2015 11:27
Adds three attributes to the client entity that determine the grant, access token, or refresh
token lifetime.  If any of the attributes is not present in the client object, the default config
value is used.

* authCodeLifetime
* accessTokenLifetime
* refreshTokenLifetime
@mjsalinger mjsalinger merged commit f8851c1 into v2-kinvey May 24, 2016
@mjsalinger mjsalinger deleted the 98-Client-Specific-Timeouts branch October 13, 2016 23:50
mjsalinger pushed a commit that referenced this pull request Aug 13, 2018
related to a NodeJS (nodejs/node#7074) and furthermore
V8 bug (https://bugs.chromium.org/p/v8/issues/detail?id=3637); replaced
seconds calculation with milliseconds.
mjsalinger pushed a commit that referenced this pull request Aug 27, 2018
related to a NodeJS (nodejs/node#7074) and furthermore
V8 bug (https://bugs.chromium.org/p/v8/issues/detail?id=3637); replaced
seconds calculation with milliseconds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant