Skip to content
Enclessa
Get started

Glossary · Operations

Single sign-on (SSO)

All termsHow Enclessa secures data

Single sign-on is an arrangement in which one identity provider authenticates a person once and then vouches for them to other applications, so that each application never handles their password.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

Also called

SSO · SAML · OIDC

What Single sign-on (SSO) means

The two protocols in general use are SAML, an XML-based standard long established in enterprise software, and OpenID Connect, a newer layer over OAuth 2.0 that is simpler to implement and now more common in new products. Most identity providers speak both, and most buyers care only that one of them works.

The security argument for single sign-on is centralisation of control. Password policy, multi-factor enforcement, conditional access and session revocation are configured once and apply everywhere, and an account disabled in the directory loses access to every connected application at the next authentication. The argument against it is concentration of risk: the identity provider becomes the single thing that must not be compromised.

Single sign-on is usually a hard procurement gate rather than a preference. Above a certain organisation size, a system that keeps its own passwords is a system the security team will not approve, regardless of what else it does well.

How Enclessa uses it

Enclessa does not support single sign-on. Sign-in is by email address and password, with account lockout and session management built in. Integration with an external identity provider through an OIDC and SAML broker is planned enterprise work in phase 5. An organisation for which single sign-on is a requirement should treat Enclessa as unsuitable today, and Enclessa states that rather than describing it as coming soon.

Where Single sign-on (SSO) is specified

Related terms

SCIMSCIM is an open standard, published as RFC 7643 and RFC 7644, that lets an identity provider create, update and deactivate user accounts in another application automatically over a REST API.Read the entryAudit logAn audit log is an append-only record of who did what, to which object, and when — kept separately from application logs so that it can be relied on as evidence rather than read as debugging output.Read the entryMulti-tenancyMulti-tenancy is an architecture in which one running installation of an application serves many independent customer organisations, each of which sees only its own data.Read the entry

Read further

The security page explains how Enclessa protects data and which certifications it does not hold. The trust centre covers the processing agreement, the subprocessors and the residency position. The FAQ answers the questions buyers ask most often.

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Create your workspaceSee pricing

Open beta. Free plan, no payment card to start.