Implementing OAuth Grant Flow
When the OAuth client in Timeline is created, the next step is to integrate one of the supported OAuth flows into your application or system. We recommend asking your developers to do it, as the whole process involves the code base on your side. Below, you will find some general information concerning such an integration and some useful links.
For instructions on how to create a new OAuth connection from Timeline's side, see Registering OAuth Client in Timeline.
Important. In Timeline 6.1, for the API the Authorization code grant is required.
Show authorization code flow steps
Implementing the flow
Implementing the Authorization Code grant depends on the technologies you use for your application or system. You can use an existing OAuth/OpenID Connect client library suitable for your technology or you can develop it yourselves.
For more detailed instructions on implementation, see Authorization Code Flow.
Using a third-party library
Timeline complies with the OAuth & OpenID standards, so any of the tools that also comply with these specifications will work. You may want to consider one of the following:
- Relying Party libraries/services from Certified OpenID Developer Tools by the OpenID Foundation - https://openid.net/certified-open-id-developer-tools/
- OAuth 2.0 libraries by oauth.net - https://oauth.net/code/
Developing it yourselves
It is possible to code a basic client yourself. For information to begin, read the specification about the Authorization Code grant in OAuth 2.0 > section-4.1 > Authorization Code grant - https://www.rfc-editor.org/rfc/rfc6749#section-4.1
From Timeline's side, you will find all the required information about its OAuth endpoints in the metadata documents. You can find them using the paths below, depending on your instance:
- https://{your.timeline.instance}.com/api/auth/oauth/.well-known/oauth-authorization-server
- https://{your.timeline.instance}.com/api/auth/oauth/.well-known/openid-configuration
9/5/2024 4:23:54 PM