Setting Up Identity Providers #

This guide walks you through setting up Pragma’s test provider and other identity providers.

Get started with Unsafe Identity Provider #

To enable the Unsafe Identity Provider, add the following:

local-dev.yml

 social:
  serviceConfigs:
    UnsafeIdentityDaoConfig:
      databaseConfig:
        username: "username"
        password: "password"
        hostPortSchema: "host-port-schema"
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Unsafe:
          class: "pragma.account.UnsafeIdentityProviderPlugin"

Get started with your identity providers #

Prerequisites:

Before integrating with Pragma Engine, you’ll need to have set up an account with a third party provider.

1. Inform third party platforms of Pragma OAuth redirect URIs #

Any identity provider that uses OAuth requires a list of authorized redirect URIs to allow the Pragma Engine platform to authenticate with it.

These are redirect URIs you’ll need to configure on the third party platform.

Example: Local development

For local development you’ll need to set these redirect URIs. For example if you were setting up Discord it would be:

http://localhost:11000/v1/account/discord-redirect
http://localhost:11000/redirect/SignInDiscord

To enable authentication for the SDK or external clients:

http://localhost:11000/v1/account/{provider}-redirect

To enable Operator Portal authentication:

http://localhost:11200/redirect/SignIn{Provider}
http://localhost:10200/redirect/SignIn{Provider}

To enable Player Portal authentication and account linking:

http://localhost:11000/redirect/SignIn{Provider}
http://localhost:11000/redirect/Link{Provider}

Example: Deployed shard environment

For a deployed shard environment for Pragma hosting you’ll need to set these redirect URIs:

To enable users to login directly through the game client:

https://{shard}.{game_name}.{studio}.pragmaengine.com:11000/v1/account/{provider}-redirect

To enable Operator Portal authentication:

https://{shard}.internal.{game_name}.{studio}.pragmaengine.com:11200/redirect/SignIn{Provider}
https://{shard}.internal.{game_name}.{studio}.pragmaengine.com:10200/redirect/SignIn{Provider}

To enable Player Portal authentication and account linking add:

https://{shard}.{game_name}.{studio}.pragmaengine.com:11000/redirect/SignIn{Provider}
https://{shard}.{game_name}.{studio}.pragmaengine.com:11000/redirect/Link{Provider}

The examples for the Player Portal authentication and account linking use the Pragma default port of 11000. If you are using the standard port 443 instead you can omit the port numbers in these URIs.

2. Configure your identity provider #

Add the relevant configuration code blocks to local-dev.yml (for testing) or common.yml (for production) under the social section.

Steam configuration

value	description
`appId`	Steam numerical value used to identify a game on Steam
`steamWebAPIKey`	authorization key used to connect with the Steam Web API
`restrictByAppOwnership`	optional boolean determining whether to reject users if they don’t own the app or are on a timed trial
`restrictByAccountBan`	optional boolean determining whether to reject users who have been developer banned or VAC banned
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Steam account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Steam:
          class: "pragma.account.SteamIdentityProviderPlugin"
          config:
            appId: "${steamAppId}"
            steamWebAPIKey: "${steamWebApiKey}"
            restrictByAppOwnership: false
            restrictByAccountBan: false
            playerLoginEnabled: true
            operatorLoginEnabled: false
            accountLinkingEnabled: true
            showPortalLoginButton: false
            visibleToOtherPlayers: true

Epic configuration

value	description
`clientId`	Epic ID that identifies developer’s Epic app while making authorization requests
`clientSecret`	encrypted OAuth secret for the Epic app referenced by the `clientId` property
`redirectUri`	optional backend authorization endpoint that Epic uses to validate OAuth handshakes
`restrictByCatalogItemOwnership`	optional boolean determining whether to reject users if they do not own the catalog item specified If set to true, the following configs must be configured: `sandboxId` and `catalogItemId`.
`sandboxId`	ID of the sandbox environment you’d like to validate against
`catalogItemId`	ID of the catalog item you’d like to validate against. Typically this will be the Game Item ID of your game.
`deploymentId`	optional This field is only required if OAuth login is enabled (portal login). ID of the deployment you’d like to validate against. For more information, refer to Epic’s documentation on Requesting an Access Token.
`playerLoginEnabled`	boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Epic account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Epic:
          class: "pragma.account.EpicIdentityProviderPlugin"
          config:
            clientId: "epic-client-id"
            clientSecret: "encrypted-epic-client-secret"
            redirectUri: "http://localhost:11200/v1/account/oauth-redirect/EPIC"
            restrictByCatalogItemOwnership: true
            deploymentId: "epic-deployment-id"
            sandboxId: "epic-sandbox-id"
            catalogItemId: "epic-catalog-item-id"
            playerLoginEnabled: true
            operatorLoginEnabled: false
            accountLinkingEnabled: true
            showPortalLoginButton: false
            visibleToOtherPlayers: true

Discord configuration

value	description
`clientId`	Discord OAuth ID that identifies developer’s Discord app while making authorization requests.
`clientSecret`	Encrypted OAuth secret for the Discord app referenced by the `clientId` property.
`redirectUri`	optional Backend authorization endpoint that Discord uses to validate OAuth handshakes.
`botToken`	optional Unique ID for Discord server bots.
`guildId`	optional Discord-defined guild identifier.
`allowedRoleIds`	optional Map of user roles that are allowed to authenticate. Discord rate limits requests using these values to 5 per second. See Discord’s Rate limits documentation for details.
`playerLoginEnabled`	optional Boolean determining whether to establish a player session with this identity provider.
`operatorLoginEnabled`	optional Boolean determining whether to establish an operator session with this identity provider.
`accountLinkingEnabled`	optional Boolean determining whether you can link accounts with this identity provider.
`showPortalLoginButton`	optional Boolean determining whether this login method is available on the portal login page.
`visibleToOtherPlayers`	optional Boolean determining whether Discord account information is visible to other players.

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Discord:
          class: "pragma.account.DiscordIdentityProviderPlugin"
          config:
            clientId: "${discordClientId}"
            clientSecret: "${discordClientSecret}"
            redirectUri: "http://localhost:11000/v1/account/discord-redirect"
            botToken: "${discordBotToken}"
            guildId: "${guildId}"
            allowedRoleIds: 
              1: "${RoleId1}"
              2: "${RoleId2}"
            playerLoginEnabled: true
            operatorLoginEnabled: false
            accountLinkingEnabled: true
            showPortalLoginButton: false
            visibleToOtherPlayers: false

Check out the Unreal and Unity Setup Guides for Discord implementation details.

Google configuration

value	description
`clientId`	Google OAuth ID that identifies developer’s Google app while making authorization requests
`clientSecret`	encrypted OAuth secret for the Google app referenced by the `clientId` property
`redirectUri`	optional backend authorization endpoint that Google uses to validate OAuth handshakes
`allowedDomains`	optional map of specific domains that are authorized for access–if this value is defined, all other domains are rejected
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Google account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Google:
          class: "pragma.account.GoogleIdentityProviderPlugin"
          config:
            allowedDomains:
              1: "${allowedDomain1}"
              2: "${allowedDomain2}"
            clientId: "${googleClientId}"
            clientSecret: "${googleClientSecret}"
            redirectUri: "http://localhost:11000/v1/account/google-redirect"
            playerLoginEnabled: true
            operatorLoginEnabled: false
            accountLinkingEnabled: true
            showPortalLoginButton: false
            visibleToOtherPlayers: false

Check out the Google developer documentation for creating access credentials.

Google Workspace configuration

Google Workspace has been added as an identity provider to support the difference between a public google authentication and an internal one.

value	description
`clientId`	Google Workspace OAuth ID that identifies developer’s Google Workspace app while making authorization requests
`clientSecret`	encrypted OAuth secret for the Google Workspace app referenced by the `clientId` property
`redirectUri`	optional backend authorization endpoint that Google Workspace uses to validate OAuth handshakes
`allowedDomains`	optional map of specific domains that are authorized for access–if this value is defined, all other domains are rejected
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Google Workspace account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        GoogleWorkspace:
          class: "pragma.account.GoogleWorkspaceIdentityProviderPlugin"
          config:
            allowedDomains:
              1: "${allowedDomain1}"
              2: "${allowedDomain2}"
            clientId: "${googleClientId}"
            clientSecret: "${googleClientSecret}"
            redirectUri: "http://localhost:11000/v1/account/google-redirect"
            playerLoginEnabled: false
            operatorLoginEnabled: true
            accountLinkingEnabled: false
            showPortalLoginButton: true
            visibleToOtherPlayers: false

Check out the Google developer documentation for creating access credentials.

Twitch configuration

value	description
`clientId`	Twitch OAuth ID that identifies developer’s Twitch app while making authorization requests
`clientSecret`	encrypted OAuth secret for the Twitch app referenced by the `clientId` property
`redirectUri`	optional backend authorization endpoint that Twitch uses to validate OAuth handshakes
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Twitch account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Twitch:
          class: "pragma.account.TwitchIdentityProviderPlugin"
          config:
            clientId: "${twitchClientId}"
            clientSecret: "${twitchClientSecret}"
            redirectUri: "http://localhost:11000/v1/account/twitch-redirect"
            playerLoginEnabled: false
            operatorLoginEnabled: false
            accountLinkingEnabled: true
            showPortalLoginButton: false
            visibleToOtherPlayers: false

Okta configuration

value	description
`clientId`	Okta OAuth ID that identifies developer’s Okta app while making authorization requests
`clientSecret`	encrypted OAuth secret for the Okta app referenced by the `clientId` property
`authorizationUri`	URI the user will be sent to for authenticatication with Okta
`tokenUri`	URI to obtain an access token by sending an auth code
`userInfoUri`	URI to obtain information about the user
`redirectUri`	optional backend authorization endpoint that Okta uses to validate OAuth handshakes
`requireEmailVerification`	boolean determining whether email is required
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Okta account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Okta:
          class: "pragma.account.OktaIdentityProviderPlugin"
          config:
            clientId: "${OktaClientId}"
            clientSecret: "${OktaClientSecret}"
            authorizationUri: "https://your-okta-subdomain.okta.com/oauth2/v1/authorize"
            tokenUri: "https://your-okta-subdomain.okta.com/oauth2/v1/token"
            userInfoUri: "https://your-okta-subdomain.okta.com/oauth2/v1/userinfo"
            redirectUri: "http://localhost:11000/v1/account/Okta-redirect"
            requireEmailVerification: true
            playerLoginEnabled: false
            operatorLoginEnabled: true
            accountLinkingEnabled: false
            showPortalLoginButton: true
            visibleToOtherPlayers: false

Auth0 configuration

value	description
`clientId`	auth0 OAuth ID that identifies developer’s auth0 app while making authorization requests
`clientSecret`	encrypted OAuth secret for the auth0 app referenced by the `clientId` property
`authorizationUri`	URI the user will be sent to for authenticatication with Auth0
`tokenUri`	URI to obtain an access token by sending an auth code
`userInfoUri`	URI to obtain information about the user
`redirectUri`	optional backend authorization endpoint that auth0 uses to validate OAuth handshakes
`requireEmailVerification`	boolean determining whether email is required
`playerLoginEnabled`	optional boolean determining whether to establish a player session with this identity provider
`operatorLoginEnabled`	optional boolean determining whether to establish an operator session with this identity provider
`accountLinkingEnabled`	optional boolean determining whether you can link accounts with this identity provider
`showPortalLoginButton`	optional boolean determining whether this login method is available on the portal login page
`visibleToOtherPlayers`	optional boolean determining whether Auth0 account information is visible to other players

social:
  pluginConfigs:
    AccountService.identityProviderPlugins:
      plugins:
        Twitch:
          class: "pragma.account.Auth0IdentityProviderPlugin"
          config:
            clientId: "auth0-client-id"
            clientSecret: "auth0-client-secret"
            authorizationUri: "https://your-auth0-subdomain.us.auth0.com/authorize"
            tokenUri: "https://your-auth0-subdomain.us.auth0.com/oauth/token"
            userInfoUri: "https://your-auth0-subdomain.us.auth0.com/userinfo"
            redirectUri: "https://localhost:11200/v1/oauth-redirect/auth0"
            requireEmailVerification: true
            playerLoginEnabled: false
            operatorLoginEnabled: true
            accountLinkingEnabled: false
            showPortalLoginButton: true
            visibleToOtherPlayers: false

PlayStation configuration

Pragma Engine supports PlayStation Network integration. Contact us for details.

Xbox configuration

Pragma Engine supports Xbox integration. Contact us for details.

For identity providers not listed, studios can implement a custom Identity Provider Plugin. See the Create Custom Identity Providers page for more information.

Setting Up Identity Providers #

Get started with Unsafe Identity Provider #

Get started with your identity providers #

1. Inform third party platforms of Pragma OAuth redirect URIs #

2. Configure your identity provider #

Helpful? Yes No

What did you like?

What went wrong?