Do we want to send cookies while making a request to the token
endpoint in order to obtain new access token using existing
refresh token. In rare cases the auth server might require the
client to send cookies along with those requests. In this case
developers will have to change this before initializing the app
like so:
FHIR.oauth2.settings.refreshTokenWithCredentials = "include";
or
FHIR.oauth2.settings.refreshTokenWithCredentials = "same-origin";
Can be one of:
"include" - always send cookies
"same-origin" - only send cookies if we are on the same domain (default)
"omit" - do not send cookies
Replaces the browser's current URL using
window.history.replaceState
API.
ONLY RELEVANT IN BROWSERS!
Generated using TypeDoc
When set to true, this variable will fully utilize HTML5 sessionStorage API. This variable can be overridden to false by setting
FHIR.oauth2.settings.fullSessionStorageSupport = false
. When set to false, the sessionStorage will be keyed by a state variable. This is to allow the embedded IE browser instances instantiated on a single thread to continue to function without having sessionStorage data shared across the embedded IE instances.