That could be anything, a stand alone service that runs on a timer, or maybe even a Lambda data action to get a fresh token followed by a Genesys Cloud data action to update the credentials (although getting it to run once at the right time seems tricky).ĭuring development you will probably want to do a get on that credential ID to get an idea what it should look like. Then you would then need something that could periodically refresh the token and update the credential via the Otherwise you could create/update your integration via API. The easiest way to get this is to open the developer console in your browser when you create the credential in the UI. The bearer token is a cryptic string, usually generated by the server in response to a login request. Use bearer tokens to authenticate grant and control permissions for entities using the Airship API, sending custom events into the system, or supporting a. You will need the ID of the credential that you configure for this. Setup the integration as a custom auth type, with the token as the only field. If there are signing / hashing / other requirements that are beyond the capability of a custom auth action then you could do something like this: A Bearer Token is a string of bytes/characters that may be opaque or have a higher-level structure that uniquely identifies a user or application of a system. If you can generate a new token in a custom auth action using the refresh token, then everything will work exactly like you want it to out-of-the-box. Access tokens may be either 'bearer tokens' or 'sender-constrained' tokens. Access tokens do not have to be in any particular format, and in practice, various OAuth servers have chosen many different formats for their access tokens. At a high level it depends on what it takes to generate the JWT. An OAuth Access Token is a string that the OAuth client uses to make requests to the resource server.
0 Comments
Leave a Reply. |