Google Workspace
This page is for the Google Workspace administrator who sets up sign-in to Seylo. You do not need to have used Seylo before.
Values you copy from Seylo into Google
Section titled “Values you copy from Seylo into Google”| Value | Example | Where it goes in Google |
|---|---|---|
| Origin | https://portal.seylo.in |
Authorized JavaScript origins |
| Sign-in redirect URI | https://portal.seylo.in/ |
Authorized redirect URIs — note the trailing / |
| Test sign-in redirect URI (optional) | https://portal.seylo.in/api/auth/sso/test/callback |
Authorized redirect URIs, second line — only for the Test tab |
Steps in Google
Section titled “Steps in Google”-
Set up the sign-in screen (once per project).
Google Cloud console (console.cloud.google.com) → pick or create a project → Google Auth platform. If it is not configured, select Get started: under Branding an app name such as
Seyloand a support email; under Audience choose Internal, so only accounts in your Workspace can sign in. -
Create the OAuth client.
Google Auth platform → Clients → Create Client. Application type: Web application. Name:
Seylo. Add the origin under Authorized JavaScript origins and the redirect URI(s) under Authorized redirect URIs. Select Create.Copy the Client secret from the dialog now: Google shows it only once, and every sign-in needs it.
Values you copy from Google into Seylo
Section titled “Values you copy from Google into Seylo”| Seylo field | Where it is |
|---|---|
| Client ID | Google Auth platform → Clients → the client. Ends in .apps.googleusercontent.com. |
| Workspace domain | Your Workspace primary domain as it appears in addresses, e.g. acme.example. Required. |
| Client secret | Required for Google. Shown once, when the client is created. Lost it? See the client secret. |
There is nothing to type for Google’s address: it is fixed. Press Check the provider, then Save provider.
The client secret
Section titled “The client secret”Google issues a Web application client for Seylo’s sign-in, and its token endpoint completes a sign-in only when the client’s secret is sent with it. A browser cannot hold a secret, so Seylo does that step on its server: your browser hands Seylo the one-time code from Google, Seylo redeems it at Google’s token endpoint with the secret you saved, and only the ID token comes back. The token is then checked as for any other provider.
The secret is write-only. Seylo stores it encrypted and never shows it
again, and when Google refuses a sign-in, its message is passed on with the
secret cut out. Once one is saved, the field says
Stored - leave empty to keep it; typing a new one replaces it.
Where to find it. Google shows the secret only once, in the dialog after Create. If you did not copy it, make another: in the Google Cloud console, Google Auth platform → Clients, open the client, and select Add secret. Paste the new secret into the provider in Seylo and select Save provider.
A Google provider saved without a secret cannot complete a sign-in:
Google refuses with client_secret is missing. Paste the secret in and save,
as above.
Test before you announce it
Section titled “Test before you announce it”Open the Test tab and use Sign in for real, which needs the test sign-in redirect URI registered in step 2. Then sign in to Seylo from another browser with a Workspace account: that is the path your people will use. See test login.
Why the domain is required: every Google Workspace on earth shares the issuer
https://accounts.google.com. The domain (the hd claim) is the only thing
that tells your organisation apart from every other Google customer, so the
registration is refused without it.
Consequence 1 — no groups, ever
Section titled “Consequence 1 — no groups, ever”A Google sign-in token carries no group and no role information, and no Google setting adds it. Groups are readable only through the Admin SDK Directory API with a service account and domain-wide delegation — a different trust model, and not part of a sign-in.
So in Seylo:
- On the Claim mapping tab set a Base role everyone in your Workspace
gets —
vieweris usual. - Give anyone who needs more a role on the Users tab, by email address. See managing users.
Consequence 2 — personal Gmail accounts cannot sign in
Section titled “Consequence 2 — personal Gmail accounts cannot sign in”A personal @gmail.com account carries no hd claim, so it is rejected. That
is intended. If someone says “I can’t sign in with Google”, first ask which
account they used.
Secondary domains
Section titled “Secondary domains”hd carries the domain of the signed-in user. If people sign in under secondary
domains, each domain in use needs its own registration — one per domain.
If it fails
Section titled “If it fails”| What you see | What it means and what to do |
|---|---|
client_secret is missing |
The client secret is not saved in Seylo, so the sign-in was redeemed without it and Google refused. Paste the client secret into the provider and select Save provider. See the client secret. |
Error 400: redirect_uri_mismatch |
Add exactly the sign-in redirect URI, including the trailing /, to Authorized redirect URIs. |
Error 403: org_internal |
The account is outside your Workspace and the audience is Internal. Use a Workspace account. |
This token carries no "hd" claim |
A personal Gmail account tried to sign in. Only Workspace accounts can. |
No tenant is registered for issuer "https://accounts.google.com" with hd="..." |
The account is from a different Workspace domain than the one saved. Compare the hd in the test report with Workspace domain (case never matters). |
FINAL: none - every action will be refused |
Expected until you grant something: set a Base role, or give the person a role on the Users tab. |
Google documentation used
Section titled “Google documentation used”Checked on 2026-10-15:
Create access credentials ·
Configure the consent screen ·
OAuth 2.0 for web server applications ·
OpenID Connect (the hd claim)