Configure Discord Authentication
To enable Discord social authentication in Web3 applications, developers must perform these three steps before integrating with the Arcana Auth SDK.
Step 1: Use Arcana Dashboard
Go to the Arcana Dashboard: https://dashboard.arcana.network
Register your dApp by creating a new dApp entry and specifying a name using the 'Create New App' wizard.
Registering the Application
If you have already registered your dApp using Arcana Dashboard and obtained an Client ID, you may skip this step.
You can choose to use defaults for other settings or change them as per your use case. For more details, see How to configure dApp Guide for details.
Go to the
Configure->Social Auth configuration section and copy the redirect URI value displayed there. This will be used in the next step to setup Discord OAuth.
Do not close the dashboard browser tab. Open another tab and set up Discord OAuth. Then revisit the Dashboard tab to complete the dApp configuration settings.
Step 2: Use Discord Developer Portal
Go to the Discord Developer Portal and create a new application.
You need to set up OAuth 2.0 credentials for your newly created dApp entry in the Discord Developer Portal. Click OAuth2 in the Discord Developer Portal LHS navigation pane, you will see the Redirects field. Specify the Redirect URI copied from the Arcana Developer Dashboard in the previous step.
Save the application settings in Discord Developer Portal.
The General Information page in the Discord Developer Portal shows a unique Application ID and a public key assigned by Discord for your application entry.
Copy the Application ID and the public key. It will be required in the next step while configuring Discord settings using Arcana Dashboard.
Step 3: Update Arcana Dashboard
Revisit the Arcana Developer Dashboard portal. Click on your app entry and visit the application dashboard. Click
Configure->Social Auth in the LHS navigation bar and refer to the "Discord" settings. Paste the Application ID and public key assigned by Discord, in the previous step as the ClientID and secret respectively.
Save the settings. Arcana Network assigns an Client ID to every registered and configured dApp. If you plan to integrate with the Arcana SDKs, you need to save this Client ID.
You are all set with the Discord configuration. Integrate the Web3 application with the Arcana Auth SDK and call the user onboarding function when the user chooses to log in.