Fanatics EcoSystem
  • Fanatics ID
  • Loyalty
  • Start Here
  • Setup
  • Single Sign On
    • Authorization
    • Code Exchange
    • Refresh Token
    • Logout
    • ID Token
    • Environments
    • Scopes
    • Account Management
    • OpenID Config
  • Server to Server
    • Authentication
    • Environments
    • Scopes
  • Point of Sale
    • Assertion Usage
Powered by GitBook
On this page
  • Query Parameters
  • Deep Links
  1. Single Sign On

Account Management

Our SSO website also hosts our account management application. A user can manage the following parts of the authentication account in this section.

Name
Description

Name

The users first & last name.

Email

Their authentication email. This is used for logging in in step 1 and for email comms.

Mobile Number

The phone number we will use for authentication related activity.

Password

The password used to log in.

Multifactor

The user can enable MFA on all logins as well as define their default method.

Logout

A user can log out of the SSO session or log out of all other sessions.

Delete Account

A user can submit a request to delete their account Note, this is not a Data Subject Request but instead is a requirement for Apple App Store submission.

Query Parameters

If you want to send a user to account management the following query parameters are supported. Be aware, you must send the ones marked as required.

Parameter
Required?
Description
Example

client_id

OAuth2 Client Identifier registered with Fanatics ID

client_id=oauth-client-id

redirect_uri

Redirection URI which the user will be sent to after completion of a workflow. Must match the scheme and host for Client registered with Fanatics ID.

redirect_uri=https://test.com/redirect

back_button_text

Text displayed for back button. If omitted, no back button will be displayed

back_button_text=Fanatics.com Displayed:"Back to Fanatics.com"

Deep Links

Deep links allow a tenant to directly access a page. Deep link redirects MUST include valid query parameters. If the user does not have an active session, a non-OAuth2 login interrupt will occur before the deep link. Once the user has an active session the deep link will continue to the page.

Route
Page

/account/edit

Edit user profile data

/account/change-email

Change user email address

/account/change-password

Change user password

/account/change-phone

Change user phone number

/account/enable-phone

Phone MFA Enablement

/account/enable-email

Email MFA Enablement

/account/manage-mfa

Manage MFA settings

PreviousScopesNextOpenID Config

Last updated 3 months ago