1. In Okta
- OIDC (recommended)
- SAML 2.0
- Sign in to the Okta admin console.
- Applications → Applications → Create App Integration.
- Choose OIDC — OpenID Connect and Web Application.
- Give the app a name (e.g. “Quippy”) and upload a logo if you like.
- Under Sign-in redirect URIs, paste the OIDC Redirect URL from Quippy.
- Under Assignments, grant access to the users or groups that should be able to sign in to Quippy.
- After saving, open the General tab and copy:
- Client ID
- Client secret
- Okta domain (used to build the issuer URL — it’s
https://<your-domain>.okta.com/oauth2/defaultfor the default authorization server).
Okta — Create App Integration (OIDC / Web Application).
2. In Quippy
Back in the admin portal’s SSO page, paste the values you just collected.- OIDC
- SAML 2.0
| Quippy field | Value from Okta |
|---|---|
| Issuer URL | https://<your-domain>.okta.com/oauth2/default |
| Client ID | App → General → Client ID |
| Client Secret | App → General → Client secret |
3. Test connection
Click Test connection in the Quippy admin portal.- OIDC success — the test returns the
authorization_endpoint,token_endpoint,jwks_uri, and whether PKCE is supported. - SAML success — the test confirms the entry point is reachable and responds with SAML metadata.
Common gotchas
Wrong authorization server → issuer mismatch
Wrong authorization server → issuer mismatch
User not assigned to the app
User not assigned to the app
Okta will return a valid sign-in session but fail the app authorization
step. Assign the user or their group to the Quippy app under
Assignments.
SAML cert pasted with extra whitespace
SAML cert pasted with extra whitespace
Strip any leading/trailing whitespace and make sure the PEM includes the
full
-----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.