10. Optional — Sign in with Cognito, Google or Box¶
Every sign-in provider only returns users to addresses you have registered with
it. Register the address shown for each provider exactly — a mismatch shows
an error such as redirect_mismatch / redirect_uri_mismatch.
Replace <domain> with your PublicBaseUrl (e.g.
https://drive.<your-domain>). The stack’s Outputs → OidcCallbackUrl
shows the first one ready-made.
Provider |
Address to register with the provider |
Where to register it |
Where to enter the IDs in QuantaCloud |
|---|---|---|---|
Amazon Cognito (“Sign in with SSO”) |
|
Cognito → User pools → your pool → App clients → your client → Login pages → Allowed callback URLs |
Stack fields |
Microsoft Entra ID / Okta / other OIDC |
|
Your provider’s app registration → redirect URIs |
Admin → Product Login → Other OIDC provider |
Google (“Continue with Google”) |
|
Google Cloud console → APIs & Services → Credentials → your OAuth client (type Web application) → Authorized redirect URIs |
Stack fields |
Box (connect Box accounts in QuantaDrive) |
|
Box Developer Console → your app → Configuration → Redirect URIs |
Stack fields |
QuantaGrid — AWS step-up SSO |
|
Nothing extra — QuantaGrid registers it with IAM Identity Center itself |
Admin → QuantaGrid → Storage Access → Amazon S3 → Redirect URI |
QuantaGrid — Azure step-up SSO |
|
Azure portal → App registrations → your app → Authentication → Redirect URIs (Web) |
Admin → QuantaGrid → Storage Access → Azure Blob |
Notes:
“Continue with Google” appears in addition to “Sign in with SSO” and the username/password form; it never replaces them.
A Cognito app client must allow
ADMIN_USER_PASSWORD_AUTH.To change stack fields later: CloudFormation → your stack → Update stack → Make a direct update → Use existing template → Next, change only the fields you need, Next → Next → tick the IAM box → Submit.