Logo/Docs

Nintendo

FusionAuth Reactor logo

This feature is only available in an Essentials or Enterprise plan. Please visit our pricing page to learn more.

Available since 1.36.0.

Overview

This section will cover how to add a Login with Nintendo button to FusionAuth. Below is an example login page with the Nintendo Identity Provider enabled.

Once you have completed this configuration you will be able to enable the Nintendo login button for one or more FusionAuth Applications. Below is an example login page with the Nintendo Identity Provider enabled.

Nintendo Login

Nintendo Developer Account

Create a new Nintendo developer account or log into the Nintendo Developer Portal with an existing account. Retrieve an existing Client Id and Client secret or follow official Nintendo documentation to request them. Contact Nintendo Developer support for additional information.

Create a Nintendo Identity Provider

To enable this identity provider for an application, find your application name in the Applications configuration section at the bottom of this panel. You will always see the FusionAuth application, this application represents the FusionAuth administrative user interface. If you wish to be able to log into FusionAuth with this provider, you may enable this application.

In the following screenshot you will see that we have enabled this login provider for the Pied Piper application and enabled Create registration. Enabling create registration means that a user does not need to be manually registered for the application prior to using this login provider.

For example, when a new user attempts to log into Pied Piper using Nintendo, if their user does not exist in FusionAuth it will be created dynamically, and if the Create registration toggle has been enabled, the user will also be registered for Pied Piper and assigned any default roles assigned by the application.

If you do not wish to automatically provision a user for this application when logging in with Nintendo, leave Create registration off. You will need to manually register a user for this application before they may Sign in with Nintendo.

That's it, now the Sign in with Nintendo button will show up on the login page for the Pied Piper application.

Nintendo Home

Form Fields

Client Idrequired
The unique client identifier obtained from Nintendo. See Nintendo Developer Portal.
Client secretrequired
The client secret obtained from Nintendo used to authenticate the request. See Nintendo Developer Portal.
Button textoptional
The text to be displayed in the button on the login form. This value is defaulted to Login with Nintendo but it may be modified to your preference.
Scopeoptional
The optional scope parameter used by Nintendo to request details about the user.
Linking strategyoptionalDefaults to Create a pending link
The linking strategy for the Nintendo provider. See Linking Strategies for more.
Reconcile lambdaoptional
A lambda maps custom claims returned from Nintendo to the FusionAuth User or Registration. To create or configure a lambda, navigate to Customizations -> Lambdas. See the lambda documentation for more.
Debug enabledoptionalDefaults to false
Enable debug to create event log entries during the user login process. This will assist you in debugging integration issues.

Options

Add Nintendo Options

Form Fields

Unique Id claimoptionalDefaults to id

The name of the claim that contains the immutable unique Id of the user.

Email claimoptionalDefaults to email

The name of the claim that will contain an email address.

Username claimoptionalDefaults to preferred_username

The name of the claim that will contain the user’s username.

Building Your Own Integration

If you are building your own login experience, you'll want to start the identity provider flow yourself and then complete the login.

You might do this if you are using the Login API rather than using the hosted FusionAuth login pages.

Completing the login is documented further in the API.

If you require a refresh token after completing the login, ensure Enable JWT Refresh is true in the application configuration. This is found in the administrative user interface by navigating to Applications -> Your Application -> Security -> Login API settings.