Configure Twitter Authentication
Web3 apps can select and enable user onboarding via Twitter by configuring the Social Auth settings in the Arcana Developer Dashboard before integrating the app with the Arcana Auth SDK.
Some of the authentication provider configuration steps are performed using the Twitter Developer Portal, whereas the others use the Arcana Developer Dashboard. After configuring Twitter, simply integrate the app with the Arcana Auth SDK, initialize the
AuthProvider, and only then add code in the app to trigger user authentication via Twitter.
When utilizing global keys in the Mainnet configuration profile, developers do not need to configure the social login section in the Arcana Developer Dashboard or set up provider-specific OAuth settings to obtain a clientID. If you are using a copy of the Testnet configuration profile as the Mainnet configuration profile, remove the Social Auth section settings altogether. Simply use the Arcana assigned Client ID for integrating the app with the Arcana Auth SDK.
Step 1: Get Redirect URI
Go to the Arcana Developer Dashboard: https://dashboard.arcana.network
Register the app by creating a new entry using the 'Create New App' wizard.
Skip this step if you have already registered your app using the Arcana Developer Dashboard and obtained a Client ID.
Go to the app configuration screen on the Arcana Developer Dashboard and click Configure > Social Auth section in the LHS. Copy the redirect URI value displayed on the top RHS. This will be used in the next step to generate Twitter authentication credentials.
Do not close the Arcana Developer Dashboard browser tab. Open another tab and set up Twitter OAuth. Then come back to the Arcana Developer Dashboard tab and complete the app configuration.
Step 2: Use the Twitter Developer Console
Go to the Twitter Developer Portal and create a new app entry for setting up the OAuth credentials for the app.
Select an appropriate environment and create a new name for the app on the Twitter Developer Portal.
In the Keys and Tokens tab, the API Key and API Key Secret values are generated automatically for your newly created app entry. Make sure you copy both of these as they will be needed later for setting up Twitter in the Arcana Developer Dashboard.
After this, you need to select OAuth Setup as shown below and configure the Redirect URI and the app deployment website domain.
When you click Setup, you will see OAuth options. For the Type of App field, select the Web App option.
In the App Info section, select the Redirect URI field. You need to specify the app callback URL in the Twitter settings as the redirect URI copied from the Arcana Developer Dashboard in the previous step.
Specify all the fields appropriately. Do not leave the optional fields empty.
- Website domain
- Organization details
- Terms of Service
Make sure you save all the settings.
If you miss copying the API Key and the API Key Secret earlier, you can go App Settings section in the Twitter Developer Dashboard. Refer to the Keys and Tokens tab. You will see under the Consumer Keys section, there is an option to regenerate the API key and secret. Make sure you copy both of these details.
These details will be required in the next step while completing the app configuration using the Arcana Developer Dashboard.
Step 3: Update the Arcana Developer Dashboard
Revisit the Arcana Developer Dashboard. View the app configuration screen. Click Configure > Social Auth in the LHS navigation bar. Refer to the "Twitter" settings and paste the API Key assigned by Twitter, in the previous step.
Save the settings. Arcana assigns an Client ID to every registered app. You need to save this Client ID and use it while integrating the app with the Arcana Auth SDK.
You are all set with the Twitter configuration. Integrate the Web3 app with the Arcana Auth SDK, onboard users and enable the authenticated users to sign blockchain transactions. See Arcana wallet Developer's Guide for details.