Airlock IAM 7.7 - Changelog

Loginapp now considers location query parameter in a URL even if accessing a target application using the application id (/ui/application/access/application-id).

SAML2 IDP: AuthnRequest IDs can now be up to 150 characters long.

Updated third-party libraries.

XML File Importer Task can be configured to continue processing after errors were encountered.

Fixed a bug where the logout disclaimer page was not shown when it was set as default target in a parameter based target URI plugin.

Updated third-party dependency libraries.

Fixed handling of HTTP responses without body.

Update JVM to 11.0.19

Updated IAM docker base image

Changed validation policy for Airlock 2FA "display_name".

Correctly rewrite locale information to conform with RFC 2616.

Fixed a bug, where configurable UIs required an input field to be submitted to the server.

Fixed token validity during daylight saving time changes.

Fixed UI handling of OAuth 2.0 or SAML 2.0 flows starting with Kerberos authentication.

Fixed "Password Authentication Step" and "Username Password Authentication Step" steps to correctly log failed password checks.

Added Event Producer for ApplyEmailChange plugin.

Security update for Apache Tomcat.

Flow Visualizer correctly handles flows with multiple identical plugins.

Default step UI for user identification step.

Kerberos/SPNEGO authentication step. See Front-Side Kerberos configuration in the Loginapp REST API.

Risk extraction based on Airlock Gateway's client fingerprinting.

HTTP Basic Authentication Step.

SAML 2.0 SP support in authentication flows. See SAML SP setup with the Loginapp REST API.

Voluntary password change step for authentication flows.

Limited support for the Office Form Based Authentication Protocol (MSOFB) with flows and Loginapp UI. See MS-OFBA configuration for the Loginapp REST UI.

Airlock 2FA factor used during login process is now available in identity propagation.

Airlock 2FA device activation in self-registration flows.

Improved control over user locking during self-registration.

Fixed phone number uniqueness check in self-registration. Public Self-Services.

Public self-service to handle links from verification emails. Emails can be sent from self-registration, public self-services, and Adminapp. See Using the Flow Continuation Step in public self-service flows.

New steps to delete all active OAuth sessions and/or remembered browsers/devices. May be used in public self-services, protected self-services, and authentication flows, e.g., after setting a new password.

Self-service for management of logged-in devices. See Browser/Device Management Self-Service (Remember-Me).

Account lock self-service. See Lockout Self-Service in the Loginapp REST API/UI.

CAPTCHAs for Loginapp REST UI (self-registration, public self-services, User Identification Step). See e.g. CAPTCHAs in the Loginapp REST API/UI.

"On-behalf login" flow identity propagator (new plugin On Behalf Login Identity Propagation).

Support for multiple transaction approval flows. See Transaction approval flow selection.

Loginapp UI translations can depend on the tenant ID.

Logout actions can depend on Gateway's session termination reason.

Added logout link to protected self-services pages.

Fixed handling of Gateway session timeouts. (CASE-33195)

New handler for sending SMS event notifications. See new plugins SMS Event Subscriber (Loginapp) and SMS Event Subscriber (Adminnapp).

Support Swisscom's SMS REST API. See new plugin Swisscom REST SMS Gateway.

Language source for event notifications is now configurable.

Include filter parameters in Adminapp JSON API response links.