Glossary

Active Config

The configuration that is currently used by the deployment.

Airlock Console

Application for → SaaS Admins to manage the Airlock SaaS Service

SaaS DevOps team (user)

Represents a person of the Airlock SaaS DevOps team that is responsible for deploying, maintaining and monitoring Airlock SaaS. They manage the infrastructure and the Airlock SaaS applications.

application

An application which is protected by authentication and authorization

authentication flow

A configurable sequence of authentication and authorization steps that determines how a user is authenticated and which access requirements must be fulfilled.

Desired Config

the configuration that is intended to be used by the deployment

deployment

A tenant's runtime. The deployment serves the end-user traffic as per the --> Active config.

end user (user)

Represents a person who accesses the customer's end-user application(s).

• Able to authenticate against the tenant Airlock IAM Loginapp.

Airlock 2FA

A strong two-factor authentication solution from Airlock that provides a ready-to-use mobile app and supporting services for second-factor authentication and transaction approval, including an offline time-based one-time passcode method.

Helpdesk (user)

An employee of the customer that is responsible for managing --> end users in customer's application landscape.

• Is an end user in a Tenant IAM (a tenant for managing the helpdesk users) with additional permission (to access the Tenant IAM Adminapp of tenants that manages the end users within his organization).

• Able to access the Tenant IAM Adminapp for end users to create, update, and (un)lock end users of that tenant.

Note: the corresponding feature has not yet been implemented and is mentioned for the sake of completeness and future reference.

Invite (a→ SaaS Admin)

The process of inviting a person as SaaS Admin into their own organization

IAM config

Generic term for the entirety of all elements that lead together to the desired behavior of an IAM: IAM configuration files, like config YAML, keystores, Design Kit ZIP, instance.properties, and more

Identity propagation
(ID propagation)

Identity information about the end-user which can be sent to the app

Identity Provider (IdP)

An (external) provider of user identities. Usually used on context of SAML 2.0 or OAuth 2.0/OIDC

Management Platform

All services, apps, and components to provide the Management Center functionality

Mobile App

An app on a smartphone, usually connected to an → application

organization

An organization is the representation of the Airlock SaaS customer and as such the contracting party and data boundary. Every user is acting on behalf of an organization. An organization is defined by it's legal name and domicile.

Protocols (Auth protocols)

Set of standards and protocols in context of authentication and authorization, e.g. JWT, SAML 2.0, OAuth 2.0/OIDC, and more

Runtime Platform

The kubernetes cluster where the end-user IAM is running

SaaS Admin (user)

An employee of the customer or Airlock Partner who is responsible for their operational security. A SaaS Admin is part of exactly one organization and is able to manage the organization, other SaaS Admins, its tenants and thereof the configurations, status and reports, and the users of the tenant. The accesses and permissions of a SaaS Admins may be restricted to a subset of above.

SaaS Superadmin (user)

A person from the Airlock SaaS DevOps team who assists --> SaaS Admins. SaaS Superadmins can manage organizations and SaaS Admins, but do not have access to tenants and their configuration or data.

Sign-up

Sign-up process of a → SaaS Admin, which also creates a new organization.

Single sign-on (SSO)

The → End-user must authenticate and authorize only once to access several apps

Staging (verb)

The process of transferring a configuration from one – Tenant into another (e.g. from TEST tenant to PRODUCTION tenant).

Stage (noun)

A staging environment (stage) is a nearly exact replica of a production environment for software testing. Staging environments are made to test codes, builds, and updates under a production-like environment before application deployment.

tenant

The tenant is the entity for the definition and operation of one configuration (and user) data set. → SaaS Admins interact with Tenants and edit their configuration.

Tenant config

Results from the settings the admin makes in the management center. → IAM config is a (partial) result of a tenant config

Tenant IAM

The Airlock IAM runtime instance assigned to a tenant in Airlock as a Service that executes the tenant-specific IAM configuration and provides authentication, authorization, identity management, and self-services for that tenant's end-users.

Tenant settings

Configuration that define the general characteristics of a tenant but is not part of the Tenant IAM config.

user

Any person interacting with the system. Usually the more specific type of a user should be used in descriptions, e.g. "SaaS Admin" or "end user"