Skip to main content
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
Nasiko signs users in through any OpenID Connect provider. Microsoft Entra ID, Okta, Google, Keycloak, AWS IAM Identity Center, and other OIDC providers all use the same flow. This guide uses Microsoft Entra ID as the worked example. A self-hosted open-source server signs users in with a username and password.

On Nasiko Cloud

On a Pro workspace, the workspace owner connects your identity provider under Settings → Security → Single sign-on. Nasiko Cloud supports Okta and Microsoft Entra ID. Connecting a provider doesn’t let anyone in by email domain: members still join by invite. On Free and Individual, saving a provider is refused with a prompt to move up to Pro. The rest of this page covers Enterprise deployments, dedicated or self-managed, where you register the provider yourself.

Where the configuration lives

You configure SSO in the dashboard under Settings → Single sign-on, or with the SSO settings API (GET/PUT /api/settings/oidc). Both need the admin role or superuser. The stored configuration is the one the server uses. A change applies to the next sign-in, with no restart. The client secret is encrypted at rest and is never returned. Reads only say whether one is set. The OIDC_* environment variables seed that configuration. On start, if no SSO configuration is stored yet and OIDC_ISSUER_URL, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, and OIDC_REDIRECT_URI are all set, the server saves them. After that, edit SSO in the dashboard or through the API. Changing the variables has no effect once a configuration is stored. nasiko-ee configure-oidc writes these variables to a deployment, so it’s for first setup. See Server configuration.
Once SSO is fully configured, the identity provider is locked. Switching to another provider would leave every user and org unit synced from the old one unmatched, so each user would be created again on their next sign-in. Settings → Single sign-on disables the picker and says so. You can still rotate the client ID, secret, and redirect URI.

Setup

1

Register an application

In Entra ID: Microsoft Entra admin center → Identity → Applications → App registrations → New registration.
  • Name: anything recognizable, for example Nasiko
  • Supported account types: single tenant, unless you need multi-tenant
  • Redirect URI: platform type Web, value https://<your-host>/api/auth/oidc/callback. It must match the redirect URI you enter in Nasiko exactly: scheme, host, path, and no trailing slash.
2

Collect issuer, client ID, and secret

From Overview: the Application (client) ID and Directory (tenant) ID. From Certificates & secrets → New client secret: copy the value immediately. It’s shown once.Entra ID issuer URL:
3

Grant API permissions

Add delegated openid, profile, and email under Microsoft Graph. They’re usually pre-granted.For directory sync, also add Group.Read.All, GroupMember.Read.All, and User.Read.All as Application permissions, and grant admin consent.To send group membership in the sign-in token, open Token configuration → Add groups claim → Security groups and keep the format as group Object IDs.
4

Save the configuration

Open Settings → Single sign-on, pick your identity provider, and fill in the issuer URL, client ID, client secret, and redirect URI. Or call the API:
When the configuration is complete, Nasiko starts a directory sync in the background so the org structure fills in without waiting for anyone to sign in. Field reference: SSO settings API.
5

Test it

Sign out of the dashboard. The sign-in page now shows a button for your provider. Or open https://<your-host>/api/auth/oidc/login. You should reach your provider’s sign-in screen, then return to Nasiko signed in.

Sign-in routes

If a sign-in fails, the browser returns to the page it came from with #error=<code> in the URL. Codes and the full request and response shapes: SSO API.

Sign in from the CLI

nasiko auth login and nasiko-ee auth login (on Enterprise deployments) sign in through the same identity provider. With no flag, nasiko auth login uses SSO when the server has it configured. --sso requires it.
Open the link, sign in through your provider if you aren’t already, check that the code matches, and click Approve. The CLI waits and saves the session when you approve. The code expires after 10 minutes. Clicking Deny, or letting it expire, ends the attempt; run the command again. The CLI uses the device sign-in routes: POST /api/auth/device/code, POST /api/auth/device/token, and the /device approval page. See SSO API.

First sign-in

A new SSO sign-in creates a Nasiko user with the member role. Nasiko never makes anyone an admin from their identity provider. An existing admin keeps that role when they sign in. If directory groups place the user in an org unit, they land there. Otherwise they sit in no unit until an admin places them, and the dashboard shows them an “awaiting assignment” screen. Place them from Access control → Org structure. See User and org management. To stop SSO from creating accounts, set SSO_MEMBERS_ONLY=true on the server. Then only users who already exist can sign in through SSO. Everyone else is turned away with the not_invited error.

Org placement from your directory

Nasiko builds its org structure from your identity provider’s groups. Each group becomes an org unit, nested groups become nested units, and group members become unit members. In Entra ID, a group’s owner becomes the unit’s lead, and a unit lead gets the manager role. Units and memberships created this way are marked as coming from the directory. Three sources feed it:
  • Sign-in. Each SSO sign-in reads the user’s groups from the token and updates their placement.
  • Directory sync (Entra ID). Nasiko reads your tenant’s groups through Microsoft Graph with the same app registration. It runs when you first save a complete configuration, and the server refreshes it periodically. It needs the Graph application permissions from Setup.
  • SCIM. Your identity provider can push users and groups directly. See SCIM provisioning.
Directory-managed placement follows the directory. You can’t remove someone from a directory-synced unit in Nasiko, because the next sync would put them back. Remove them from the group in your identity provider instead. Units and placements you create by hand in Nasiko are never touched by a sync. The Identity provider card on Access control → Org structure (admins) shows the detected provider, whether it runs in full mode (directory groups available) or flat mode (sign-in only, no directory), when the group tree last synced, and which permissions it needs. Reset organization data removes every directory-synced unit and membership and resets those users, other than admins, to member. Units you created by hand stay, and sign-in keeps working. The next directory sync or SCIM push restores the directory structure. API: Identity provider.

SCIM provisioning

SCIM 2.0 lets your identity provider create, update, and deactivate Nasiko users and groups as they change in your directory. SCIM becomes available once SSO is fully configured.
1

Copy the tenant URL

In Settings → Single sign-on, under SCIM provisioning, copy the tenant URL: https://<your-host>/scim/v2. Paste it into your provider’s SCIM Tenant URL field.
2

Generate a token

Click Generate new token. Copy the token immediately: it’s shown once. Paste it into your provider’s Secret Token field. Each token is tied to your configured identity provider, and it’s rejected if you later configure a different provider.
3

Start provisioning

Turn on provisioning in your identity provider. Users and groups appear in Nasiko as the provider pushes them.
What a push does in Nasiko: Active tokens lists each token with its creation date, last use, and provider. Revoke a token there to cut off its provider immediately. Each token is limited to 300 requests a minute. API: SCIM API.