Constructs the query parameters for the Rev /oauth/authorization endpoint
OAuth signing settings, retrieved from Rev Admin -> Security -> API Keys page, along with revUrl
optional state to pass back to redirectUri once complete
A valid oauth flow endpoint + query
Parse the query parameters returned to the redirectUri from Rev
The URL with query parameters, or object with the query parrameters
generate the Authorization URL for the OAuth2 flow as well as the codeVerifier for the subsequent Access Token request. You must store the codeVerifier somehow (i.e. serverside database matched to user's state/cookies/session, or on browser SessionStorage) to be able to complete the OAuth2 login flow.
OAuth signing settings, retrieved from Rev Admin -> Security -> API Keys page
optional state to pass back to redirectUri once complete
Optional
verifier: stringthe code_verifier to use when generating the code challenge. Can be any string 43-128 characters in length, just these characters: [A-Za-z0-9._~-]. If not provided then code will automatically generate a suitable value
A valid oauth flow URL + the code_verifier to save for later verification
OAuth signing settings, retrieved from Rev Admin -> Security -> API Keys page
Secret from Rev Admin -> Security. This is a DIFFERENT value from the User Secret used for API login. Do not expose client-side!
optional state to pass back to redirectUri once complete
A valid oauth flow URL
Optional
options: RequestOptionsOptional
options: RequestOptionsOptional
options: RequestOptionsOptional
options: RequestOptionsOptional
options: RequestOptions
Authentication API methods Generally you won't need to call these methods directly - RevClient instances use them internally to maintain an authentication session.
The exception is the AuthAPI.buildOAuth2Authentication and AuthAPI.loginOAuth2 methods, which can be used when building an OAuth2 authentication flow.
See
Auth API Docs