10. Set up each feature after install

Do only the parts the customer uses. Each part lists what to prepare, the exact steps, and what the common error means. Throughout, <domain> is your PublicBaseUrl, e.g. https://drive.<your-domain>.

Note

Why these steps exist. These features live partly in other systems — Google, Microsoft Azure, Box, Amazon Cognito. The stack cannot set them up there for you. Two rules prevent almost every error: 1. Register your own domain’s address with each provider. A new domain must be added again, even if an older one already works. 2. Put each secret in the right place. Secrets go into the stack fields; the Admin Console only takes the name of a secret (GOOGLE_CLIENT_SECRET, COGNITO_CLIENT_SECRET), never the secret.

How to change stack fields (needed below only if you skipped Step 6b and left the Cognito or Google fields empty at install): CloudFormation → your stack → Update stack → Make a direct update → Use existing template → Next, change only the fields named, Next → Next → tick the IAM box → Submit. The status shows UPDATE_IN_PROGRESS for about 5–15 minutes (click refresh now and then); wait for UPDATE_COMPLETE before testing. If QuantaCloud is switched off, switch it on first.

10.1 Sign-in options: up to three side by side

Admin → Authentication → Product login sets all three, and the sign-in page shows them together:

  1. Username and password: always there (an admin can limit it to administrators with Allow password sign-in).

  2. Sign in with SSO: one provider (Amazon Cognito, Microsoft Entra ID, Okta…), the Sign in with SSO card (10.3, 10.4).

  3. Continue with Google: its own section further down the same page (10.2). It never replaces SSO.

The Qdrive desktop app offers the same options, each only when it is on here: Continue with Google and Sign in with SSO open the user’s browser, and Qdrive continues signed in. It uses the same callback address, so Google and your SSO provider need no extra setting. With Allow password sign-in off, desktop users sign in with SSO too. A server on a release older than 29 October 2026 cannot finish a desktop browser sign-in; Qdrive then offers username and password only.

10.2 Google sign-in (“Continue with Google”)

Prepare: a Google Cloud project you can edit.

  1. Google Cloud console → APIs & Services → Credentials → Create credentials → OAuth client ID, type Web application. Under Authorized redirect URIs add <domain>/admin-api/auth/oidc/callback (the Admin Console shows this exact address) → Create. Copy the Client ID and the Client secret (it starts with GOCSPX-).

  2. Admin → Product login → Continue with Google: paste the Client ID and the Client secret → Turn on. No stack update is needed.

  3. Open the sign-in page: Continue with Google appears beside the other options.

Note

The stack fields GoogleClientId / GoogleClientSecret (install form Section 4) do the same job and take priority when filled; the Admin Console then shows On (set in the stack). Use one or the other.

Error

Meaning and fix

Client ID must look like …apps.googleusercontent.com

That is not a Google Client ID (often the Cognito one). Copy it again from Google.

Client secret must be the Google secret, starting with GOCSPX-

A name or another secret was pasted. Copy the Client secret from Google.

Google says redirect_uri_mismatch

The address in step 1 is missing or differs. Add it exactly.

Sign-in page shows only Google, no SSO

An older setup saved Google as the SSO provider. Set Sign in with SSO back to your provider (or Local credentials) and use the Google section instead.

10.3 Amazon Cognito (“Sign in with SSO”) and SaaS users

Prepare: a Cognito user pool and an app client. The app client must allow ADMIN_USER_PASSWORD_AUTH.

  1. Cognito → User pools → your pool → App clients → your client → Login pages → Edit → Allowed callback URLs → Add another URL: <domain>/admin-api/auth/oidc/callback → Save changes.

  2. On the same app client page click Show client secret and copy it.

  3. Stack fields (section 4. Sign-in): CognitoUserPoolId (e.g. us-east-1_AbCdEf123), CognitoClientId, CognitoClientSecret.

  4. Admin → Product login → Other OIDC provider:

    • Issuer URL: https://cognito-idp.<region>.amazonaws.com/<pool id>.

    • Client ID: the app client ID.

    • Redirect URI: <domain>/admin-api/auth/oidc/callback.

    • Client secret reference: type exactly COGNITO_CLIENT_SECRET.

    • Save changes.

  5. Sign out and click Sign in with SSO.

  6. SaaS users (Admin → Users → SaaS (Cognito)) work once step 3 is done: invite users from there.

Error

Meaning and fix

Cognito page Something went wrong, URL contains redirect_mismatch

Your domain is not in Allowed callback URLs (step 1). Every new domain needs its own line.

The OIDC client secret is unavailable

Step 3 or the reference in step 4 is missing.

SaaS tab: Cognito is not configured on this server

Step 3 is missing.

10.4 Microsoft Entra ID, Okta or another OIDC provider

  1. In the provider’s app registration, add the redirect URI <domain>/admin-api/auth/oidc/callback.

  2. Admin → Product login → Other OIDC provider: the provider’s Issuer URL, Client ID, Redirect URI as above. Leave Client secret reference empty for a public client; for a confidential client contact support for the name of the setting that holds its secret.

10.5 QuantaGrid storage: AWS and Azure, Static or SSO

Admin → QuantaGrid → Storage access sets one access mode per cloud: Static (one shared access for everyone) or Step-up SSO (each user signs in with their own cloud account).

AWS, Static: nothing to do. QuantaGrid uses the stack’s own security role and shows the S3 buckets of the AWS account the stack runs in. Never type AWS access keys; the page refuses them.

AWS, Step-up SSO: fill your IAM Identity Center store ID and start URL; Redirect URI = <domain>/grid/sso/aws/callback. QuantaGrid registers that address itself.

Azure, Static:

  1. Azure portal → App registrations → New registration (or your existing app). Copy the Application (client) ID and Directory (tenant) ID.

  2. Certificates & secrets → Client secrets → New client secret → Add. Copy the Value column at once — Azure shows it only now. Do not copy the Secret ID (a code with dashes); the Value contains a ~.

  3. Storage account → Access control (IAM) → Add role assignment → Storage Blob Data Contributor (or Reader for read-only) → assign it to the app.

  4. Admin → QuantaGrid → Storage access → Azure Blob → add a connection: Tenant ID, Client ID, the secret Value, storage account name → Save.

Azure, Step-up SSO: in the app registration → Authentication → Add a platform → Web → Redirect URIs: <domain>/grid/sso/azure/callback. Each user needs a Storage Blob Data role on the storage account.

Error

Meaning and fix

Azure Cannot connect / Azure rejected the client secret

The Secret ID was pasted instead of the Value (step 2). Make a new secret and paste its Value.

Azure does not know this Client ID / Tenant ID

Check the IDs from step 1.

Connects, but listing fails with a permissions message

Step 3 (role assignment) is missing.

Microsoft page AADSTS90102: ‘redirect_uri’ value must be a valid absolute URI (Azure SSO)

The Step-up SSO Redirect URI is empty or incomplete. Type exactly <domain>/grid/sso/azure/callback (with https://), Save, register the same address in the Entra app, then Test & validate.

QuantaGrid still says Static after enabling SSO

SSO switches users only after Test & validate passes; until then everyone stays on Static on purpose.

10.6 Box connector

QuantaDrive imports Box files two ways; set up either or both in Admin → QuantaDrive → Connectors → Box. Each needs its own Box app.

Per-user (OAuth): each user connects their own Box account.

  1. Box Developer Console → Create New App → Custom App → User Authentication (OAuth 2.0).

  2. Configuration → OAuth 2.0 Redirect URIs: add <domain>/api/v1/connectors/box/callback (the Connectors page shows it with a Copy button) → Save Changes.

  3. Copy the Client ID and Client Secret from the same page.

  4. Admin → Connectors → Box → Per-user (OAuth): paste both → Save config → Test → Enable OAuth.

Single account (JWT): one shared Box account for everyone. Needs a Box Enterprise account (a free personal account has Enterprise ID 0 and cannot work).

  1. Box Developer Console → Create New App → Custom App → Server Authentication (with JWT).

  2. Configuration → Add and Manage Public Keys → Generate a Public/Private Keypair. Box downloads a JSON file — use this file; it contains the private key.

  3. Your Box administrator authorizes the app: Box Admin Console → Apps → Custom Apps Manager → Add App → the app’s Client ID.

  4. Admin → Connectors → Box → Single account (JWT): paste the whole downloaded JSON → Save config → Test → Enable JWT.

  5. Read files as: leave empty, or type a real Box user’s email.

Error

Meaning and fix

Box page Application Error, invalid_client

The Client ID is not from a User Authentication (OAuth 2.0) app, or ID and secret come from different apps. Do OAuth steps 1–4.

Box says redirect_uri_mismatch

OAuth step 2 is missing or differs.

Config is missing … publicKeyID, privateKey, passphrase

The JSON was downloaded without a keypair. Do JWT step 2 and paste the new file.