Apps and credentials
Everything about the app you create in the developer console.
Public or confidential
| Type | Use it for | Credentials |
|---|---|---|
| Public | Games, desktop and mobile apps, single-page web apps, consoles. Anything a player can take apart. | Client id only. Browser sign-in must use PKCE. |
| Confidential | Your own web server or backend that keeps secrets out of players' hands. | Client id and client secret. |
The client secret is shown once, when you create the app or rotate the secret. REAN only keeps a fingerprint of it.
Redirect URIs
Browser sign-in returns the player to a redirect URI you registered. REAN compares it exactly (including the path and query), with one exception for desktop apps.
| Allowed | Example | Notes |
|---|---|---|
| HTTPS | https://yourgame.com/auth/callback | Websites and web apps. |
| Loopback | http://127.0.0.1/callback | Desktop apps. Register it without a port; any port is then accepted at sign-in (RFC 8252). |
| Localhost | http://localhost:3000/callback | Local development. The port must match. |
| App scheme | com.yourstudio.game:/oauth | Mobile and desktop apps (reverse-domain scheme). |
Up to 10 redirect URIs per app. Fragments (#…) are not allowed.
Scopes your app may request
In the console you choose which scopes your app is allowed to ask for. A sign-in request asking for anything else is refused with invalid_scope. Ask players only for what you use: smaller requests are approved more often.
Launcher sign-in
Letting the REAN Launcher start your game and sign the player in is enabled by REAN for games distributed through the launcher. Contact us from the support page with your client id.
Limits and requirements
- Your REAN account email must be verified to create apps.
- Up to 10 apps per developer account.
- App names are 2–40 characters and must not contain “REAN”, so players never confuse your app with ours.
- You must accept the developer terms.
- Deleting an app signs every player out of it and cannot be undone.