Dashboard

To delete an application in the Arcana Developer Dashboard:

• You need to be logged into the dashboard.
• In the Manage Apps dashboard screen, select the card displayed for your registered application.
• Click the trash icon on the top right to delete the app entry.
• Your application registration will be canceled and the Client ID assigned to your application will no longer work

To migrate an application from Arcana Testnet to Mainnet, follow these steps:

1. Use the Arcana Developer Dashboard, visit the 'Manage App' dashboard page, and select the application entry. By default, when you register any application, a 'Testnet' configuration profile is created for the application. Click on the app card to see the application configuration dashboard screen.

2. On the application configuration dashboard screen, switch the network from 'Testnet' to 'Mainnet' on the top right to create a 'Mainnet' configuration profile. You will be asked to approve the creation of the 'Mainnet' configuration profile. To begin with, this is a copy of the 'Testnet' profile but you can edit and manage it independently. Note that a new Client ID is assigned to the 'Mainnet' profile.

3. Use the 'Mainnet' profile Client ID in your integration code instead of the earlier one which corresponds to 'Testnet'. You will need to restart your application after this change. This is important. If you fail to make this change, even if you have switched the profile in the dashboard, your application will continue to use the 'Testnet' configuration settings.

Yes, developers can run two instances of the app simultaneously, one on the Arcana Testnet and the other on the Mainnet as each app instance is assigned a unique Client ID.

Use the 'Mainnet' configuration profile Client ID in your app's Auth SDK integration code and instantiate the AuthProvider. Then deploy this app instance to use Arcana Mainnet.

Similarly, use the 'Testnet' configuration profile Client ID in another copy (branch / different version of the code) of your app where Auth SDK is integrated and instantiate the AuthProvider. Then deploy this app instance to run it using the Arcana Testnet.

Once you have enabled 'Mainnet' for an application, you cannot delete the 'Mainnet' configuration profile independently in the current release. You can switch your application from 'Mainnet' to 'Testnet' by using the dropdown button in the application configuration screen to edit or modify it.

The only way to delete Mainnet settings is to deregister the app and delete the app entry altogether. This removes both Testnet and Mainnet configuration profiles. You will need to re-register the application. This will create a totally new Client ID and you will be required to specify this new Client ID when integrating your application with the Auth SDK. As a result, when you deploy your app and the users log in, they will see brand-new wallet addresses.

If you wish to ensure that the user wallet address does not change, you must register your application and request for the 'Shared Key Space' option at the very start. In that case, users will be allowed to use the same wallet address across all applications in the Arcana ecosystem and even if an application is de-registered and re-registered.

Make sure the file is less than the 1 MB limit for a successful upload.

Click on the 'x' icon next to the uploaded logo file. You will see a notification about the successful deletion of the file. Click on the upload icon and upload a new logo file.

If you do not specify any social authentication configurations in your 'Testnet' or 'Mainnet' configuration profile settings in the Arcana Developer dashboard, then your app can only onboard users via the passwordless option that is enabled by default. You can use the plug-and-play UI via the connect method or build your own auth UI and use the loginWithLink method to onboard users via the passwordless login option.

To enable any social providers for app onboarding you must configure them using the dashboard. See the how to configure social providers guide for more details.

Yes. The application developer can enable one or more social authentication mechanisms and passwordless login. The application users can choose any one of the supported authentication mechanisms to log in easily similar to Web2 app onboarding.

When integrating with the Arcana Auth SDK, the application developer can use the alwaysVisible setting to control whether the Arcana wallet UI is automatically displayed once the user has authenticated (default) or whether it shows up only when a blockchain transaction is triggered that requires the user's approval.

If alwaysVisible = false during AuthProvider instantiation and Auth SDK integration with the app, the wallet will only appear when a blockchain transaction is triggered. The wallet screen will pop up, requesting the user's approval or signature. Once the user takes the appropriate action, the wallet screen will disappear.

For more details, see Arcana wallet visibility modes

This is an optional setting for additional security. If specified, the Arcana Network Auth subsystem uses this setting to restrict the Arcana wallet from loading anywhere else other than the application website domain that a developer specifies. for restricted domains, the frame-ancestor Content Security Policy (CSP) is used.