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
  • Clients
  • Fields

Setup

PreviousStart HereNextSingle Sign On

Last updated 3 months ago

There are a number of setup tasks that need to be performed by the Fanatics team before you can use our services. Please make sure you have worked with the Fanatics EcoSystem team to get your account setup.

Clients

The OAuth framework requires the registration of as a mechanism for identifying what tenant is using the authorization service. When you register a client you must supply one of more where we redirect the user to after they successfully complete their authentication.

Fields

Parameter
Provided By
Description

client_id

Fanatics

This identifies the client. This will be sent as a url parameter to our SSO.

client_secret

Fanatics

This is a secret known only to your application and our authorization server. This is essentially a password that should be stored as securely as possible and only sent between your backend server and our authorization server.

redirect_uri

You

After a user successfully authorizes your application, the authorization server will redirect the user back to this redirect_uri. Be aware that to reduce the chance of certain client side attacks the spec requires the redirect uri to be a complete match (even trailing slashes). Please note, we support multiple redirect URIs for a single client.

OAuth Clients
Redirect URIs