Authenticating to Arkane is done using OpenID Connect, which combines the OAuth 2.0 protocol together with a simple identity layer. We use OpenID Connect's Authorization Code Flow for our authentication and authorization.
If you provide your own implementation of
bearerTokenProvider, the web3 provider will not attempt to obtain an authentication code, but rather use the one provided by you.
In order to communicate with Arkane, a Client ID is required. To connect to our staging environment and use the testnets, we provide a public Client ID
Arketype which is free to use and available to anyone.
To connect to our production environment and the different mainnets, a private Client ID is required. By using a Client ID that is linked to your application, an extra level of security is added, as it allows transaction filtering based on domain. It also allows for custom branding of the Widget.