Organization SSO (OIDC)
With single sign-on, people sign in to Tara with your company identity provider (Okta, Microsoft Entra ID, Keycloak, or any OpenID Connect provider). You set it up from Settings › SSO, and it is yours: no PhillipCLI staff involved. Owners and Admins can do it.
People then pick Sign in with SSO on the login page and enter the organization's slug, their work email, or the email domain. From the terminal, run ph login --sso <org>.
This page is for your own organization on the shared service. If you run Tara yourself and want one provider for the whole install, see Sign-in with SSO (OIDC).
Set up
- At your provider, create an OIDC application of the web (confidential) type, and register this callback URL:
https://tara.phillipcli.cloud/auth/sso/<org>/callback, where<org>is your organization's slug. - In Tara, open Settings › SSO and paste the issuer, the client ID, and the client secret. Tara fetches the provider's configuration and signing keys first, and saves nothing if that fails.
- Run the test. It must succeed before you can require SSO.
- Choose the role for people who sign in for the first time: Viewer, Member, or nobody (never Admin or Owner).
- Optionally, turn on Require SSO.
The secret is stored encrypted and is never shown again. Tara shows only that a secret exists.
Okta
Create an OIDC - OpenID Connect app of type Web Application, with the callback above as the sign-in redirect URI. Assign it to the people or groups who may sign in. The issuer is your Okta domain, or the authorization server's address if you use a custom one: https://<your-company>.okta.com or https://<your-company>.okta.com/oauth2/default.
Microsoft Entra ID
Under App registrations, create a registration, add a Web redirect URI with the callback above, and create a client secret under Certificates & secrets. The issuer is https://login.microsoftonline.com/<tenant-id>/v2.0. The client ID is the Application (client) ID. Under Enterprise applications, you can limit who may sign in.
Keycloak
Create a client of type OpenID Connect, turn on Client authentication, and enable only the standard flow. Put the callback in Valid redirect URIs. The issuer is https://<keycloak>/realms/<realm> (Keycloak before version 17 adds /auth). Copy the secret from Credentials. Users need an email address.
Using a SAML-only provider, AD FS, or Google Workspace? See Use SAML identity providers through OIDC.
From the terminal, the same steps are:
echo "$CLIENT_SECRET" | ph org sso set --issuer https://sso.example.com/realms/acme \
--client-id tara --client-secret-stdin --jit-role member --enable
ph org sso test
ph org ssoph org sso shows the issuer, the callback URL to register, the test result, and whether SSO is required.
Who joins and with which role
The first time someone signs in through your provider, Tara adds them to your organization with the role you chose (Viewer, Member, or nobody). It respects the seat limit (Viewers are free), never changes the role of someone who is already a member, and doesn't add back someone an Admin removed. To give someone a higher role, change it in Members.
Require SSO
Turn this on once the test passes and you have a verified domain. Members whose verified email (GitHub, Google, or email link) is at your verified domain must then come in through your SSO. For your organization they get sso_required, and the Portal sends them to SSO. Their personal space and other organizations keep working. If you change the issuer, client ID, or secret, Tara turns the requirement off again until you test.
Owners are always exempt. If your provider breaks, an Owner signs in the usual way and turns it off: ph org sso enforce off.
People who already have an account link it once, with Link my account in Settings › SSO (the Portal offers it when it sends them to SSO). SSO then opens their existing account instead of creating a new one.
What an SSO session can do
Your provider is controlled by your organization, so Tara treats what it says with care.
- An SSO session sees only your organization. It can't open the person's other organizations.
- No writing to the personal store. A session, CLI session, or token that came through your provider can't publish, submit, import, contribute, change visibility, or deprecate anything in the person's personal store. Tara answers
sso_session_personal. To change personal resources, sign in with GitHub, Google, or email. Reading still works. - Tokens only for your organization. It can create tokens for your organization only, and can't link another provider.
- Never linked by email. The email an SSO identity claims never links to an existing account, and isn't treated as verified. See Sign-in options.
If Tara can't reach the provider, check that the issuer is a public https address. Tara refuses private and internal addresses.
Provision users with SCIM
SSO decides who can sign in. To have your identity provider also create, suspend and remove people and set their roles from groups, use SCIM 2.0: Okta or Microsoft Entra ID. SCIM does not sign anyone in, so SSO stays needed. SCIM is included in the Enterprise plan.
Remove SSO
ph org sso remove --yes. People can no longer sign in through your provider, and Require SSO turns off. Members keep their membership and their other sign-in methods.