Skip to content

Access and SSO ​

Space authenticates users independently. Give it a separate domain and SAML client. A cookie from the Orpheus web interface does not grant Space access. Configure each application's user access in the IdP.

Access mode ​

Set ORPHEUS_BROWSER_AUTH on the Space API.

ModeBrowserAPI key
api_onlyNo cookie accessRead and write
anonymousRead and write without loginRead and write
samlRead all schedules, write according to ownershipRead and write

Use anonymous on an isolated local stack. This mode and valid API keys retain full access to all schedules and their owners.

Exact API, Origin and CSRF rules.

Schedule permissions ​

All signed-in users can read every schedule, its history and results. Configure administrators through access.admin_emails:

toml
[access]
admin_emails = ["admin@example.com"]
  • Administrators can create and change any schedule, including assigning or clearing its owner.
  • Other users can create only for themselves and change only their own schedules. They cannot transfer ownership or claim a shared schedule.
  • Schedules without an owner are read-only for ordinary users.
  • A session without a valid email can only read.

These rules apply to editing, manual runs, pause/resume, deletion and context reset, including direct cookie-authenticated API requests. API keys retain full access. With an omitted or empty administrator list, no browser user has administrator rights. Restart the API after changing the list. Existing sessions use the new permissions without signing in again.

Configure SAML ​

Supply these SAML settings to the Space API:

dotenv
ORPHEUS_BROWSER_AUTH=saml
ORPHEUS_PUBLIC_URL=https://space.example.com
SAML_SP_ENTITY_ID=orpheus-space
SAML_IDP_METADATA_FILE=/etc/orpheus-space/idp.xml
SAML_SP_CERT_FILE=/etc/orpheus-space/sp.crt
SAML_SP_KEY_FILE=/run/secrets/space-sp.key
BROWSER_SESSION_TTL_SECONDS=43200
  1. Prepare an SP certificate and its matching private key.
  2. Create a separate SAML IdP client with entity ID orpheus-space. Admit the intended employee group.
  3. Set the ACS to https://space.example.com/auth/callback with HTTP-POST binding.
  4. Configure request signature verification with the SP certificate and SHA-256 signing of responses/assertions.
  5. Configure a stable NameID and AuthnStatement, as in Orpheus SSO setup.
  6. Supply a SAML attribute with Name or FriendlyName email. In Keycloak, add a User Property mapper from user property email to SAML attribute email. This email determines schedule ownership and administrator rights. The IdP must verify it and prevent users from assigning themselves arbitrary email addresses.
  7. Export IdP metadata, mount it along with the certificate and key in the API, then restart the API.
  8. Open Space, sign in and create a paused schedule. SP metadata is available at /saml/metadata.

Space also accepts an email-format NameID. A missing or invalid email does not prevent login, but the session is read-only. After changing the mapping, sign out of Space and sign in again to refresh the session email.

You can reuse Orpheus's SP certificate/key pair if the Space client also has it registered. Application domains, clients and browser sessions remain separate. The Space worker does not need SAML files.

Sign out ​

Signing out ends the local Space session. IdP and Orpheus web-interface sessions remain active, so a subsequent login may not require a password.

Use IdP rules to grant application access and the administrator list to grant full schedule access. The agent skill uses an API key with full access and separately follows the request author’s identity.