Add possibility to connect using known/stored OpenID access token and cluster #137
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.
Adds the possibility to optionally pass a known access token and cluster to OpenIdConnectAuthentication.
Designed to be a non-breaking change.
In my use case a cron job is running every 45 minutes to refresh my access token and cluster, which are then stored. When a connection to the API is required the tokens, expiry time and cluster are retrieved and used to connect to Twinfield.
Connection takes about 2 seconds less this way and lessens the total amount of calls to Twinfield when connecting more than 20-30 times/day.
Example:
Cron Job running every 45 minutes:
Connection: