Documentation

Updated

Your own provider apps

By default, people who sign in to your tenant with Google, Microsoft or Apple approve algizian's shared app, so the provider's consent screen names algizian. If you would rather it shows your own name, register your own app with the provider and give algizian its credentials. Your users then consent to you, and the sign-ins count against your own app's quota.

This is optional and per provider: a provider without your credentials keeps using the shared app, and you can go back at any time.

Before you start

  • With your own app the provider returns the user to your own sign-in host, so you register redirect URIs on your hosts: https://<slug>.algizian.com/cb/<provider> and, if you use a custom domain, https://login.example.com/cb/<provider> (provider is google, microsoft or apple). Register every host people sign in on; one is enough if you use only that host. The answer to the call that sets your credentials lists the exact addresses for your tenant.
  • Request only the identity scopes: Google: openid, email and profile; Microsoft: openid, email and profile; Apple: name and email.
  • You give the credentials to algizian with PUT /tenants/{tenant}/providers/{provider}/credentials or the set_provider_credentials tool, see the management API and MCP. The secret is stored encrypted and is never returned or logged. The same guides are available to your tools as GET /providers and GET /providers/{provider}/setup.

Google

  1. In the Google Cloud console create or pick a project, then open Google Auth platform (APIs and Services, OAuth consent screen).
  2. Branding: set the app name (this is what users see), support email and logo.
  3. Audience: choose External. Move the app to In production. While it is in testing only listed test users can sign in and the approval lapses after a week.
  4. Data access: add only openid, email and profile. These are not sensitive scopes, so no Google review is needed.
  5. Clients: create an OAuth client of type Web application and add each authorized redirect URI from the answer, for example https://acme-games.algizian.com/cb/google. Leave JavaScript origins empty.
  6. Copy the client id (it ends in .apps.googleusercontent.com) and the client secret, and send them:
{ "clientId": "123456-example.apps.googleusercontent.com", "clientSecret": "..." }

Microsoft

  1. In the Microsoft Entra admin center open App registrations and choose New registration.
  2. Name it (shown on the consent screen) and choose the supported account types Accounts in any organizational directory and personal Microsoft accounts.
  3. Add a Web redirect URI for each of your hosts, for example https://acme-games.algizian.com/cb/microsoft.
  4. Certificates and secrets: create a client secret and copy its Value (not the secret id). Secrets expire, at most after 24 months: note the date, and replace the credentials before then.
  5. API permissions: Microsoft Graph delegated openid, email and profile. No admin consent is needed.
  6. Token configuration: add the optional claim xms_edov to the ID token. Without it a Microsoft email is never treated as verified, so a returning person will not be matched to an existing account by email.
  7. Send the Application (client) ID (a GUID) and the secret value:
{ "clientId": "00000000-0000-0000-0000-000000000000", "clientSecret": "..." }

Apple

  1. In your Apple Developer account create an App ID with the Sign in with Apple capability, then a Services ID. The Services ID (for example com.example.signin) is the client id.
  2. Open the Services ID, enable Sign in with Apple, choose the primary App ID, and under Website URLs add your sign-in host as the domain (for example acme-games.algizian.com) and its return URL (https://acme-games.algizian.com/cb/apple); add the custom domain the same way if you use one. Apple verifies a domain by fetching a file from it: download the file and send its contents as domainAssociation below, and algizian serves it at /.well-known/apple-developer-domain-association.txt on your hosts. Apple accepted a subdomain of a domain already registered on our own team without a verification file; this path has not been tested with a second Apple team.
  3. Under Keys create a key with Sign in with Apple enabled and download the .p8 file (Apple shows it once). Note the 10-character key id; your team id is on the membership page.
  4. Send the Services ID, team id, key id, the contents of the .p8 file and the verification file:
{ "clientId": "com.example.signin", "teamId": "ABCDE12345", "keyId": "FGHIJ67890", "privateKey": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----", "domainAssociation": "..." }

algizian signs Apple's short-lived client secret itself with your key.

What changes for existing users

Switching a provider between the shared app and your own changes the provider's account id (sub) for your users:

ProviderAccount id
Googlethe same in every app
Microsoftdifferent per app registration
Appledifferent per developer team

algizian recognises a returning user by that id first and by a verified email second (Google and Apple state it; Microsoft only with the xms_edov claim). A user who cannot be matched either way gets a second account. So switch before you have many users, or expect duplicates for Microsoft and Apple users without a verified email. Users you imported with a provider id must be imported again with the id your own app produces. The call that sets or removes credentials returns this as a warning.

Privacy

With your own app, you are the party the person consents to when they sign in. Your privacy notice should say what you receive (an identifier, email and name) and that algizian processes sign-ins on your behalf.