JSP-Loginapp Deprecation Announcement

Up to (and including IAM 7.7), Airlock IAM provides the JSP-Loginapp and its dedicated successor Loginapp UI as a web front-end for all end-user interactions via a web browser. The JSP-Loginapp will be removed in Airlock IAM 8.0 in favor of the REST API-based Loginapp UI.

This article provides the most important information for customers using the old JSP-Loginapp.

When will the JSP-Loginapp be removed?

IAM 7.7 is the last version that contains the JSP Loginapp. IAM 8.0 is scheduled for spring 2023 and will no longer contain the JSP-Loginapp.

Discontinuation announcement for JSP Loginapp

What part of Airlock IAM will be removed?

Within the Loginapp module, Airlock IAM provides two types of web frontends for end-user interactions using a web browser:

Loginapp types




Old web frontend based on Java Servlets, Java Server Pages (JSPs), and Authenticator plugins.

This is the old type of Loginapp that has existed since the first version of the product.

(see schedule above)

Loginapp UI

Modern and more flexible Angular-based web frontend using the Loginapp UI and based on flows.

This is the new type of loginapp that has been introduced with IAM 7.1. It has been and is constantly being expanded and offers most of the functions of the old Loginapp and already partly surpasses it with new functions.


With IAM 8.0 the JSP-Loginapp will be removed. This includes:

  • JSP pages and templates
  • Servlets used to serve the JSP pages
  • Plugins exclusively used with JSP pages (especially includes part of the Authenticator plugins)

Therefore, all deployments using the JSP-Loginapp must be migrated to the new Loginapp UI.

What does this mean for existing Airlock IAM projects?

Since all JSP-based parts of the Loginapp will be removed with IAM 8.0, existing IAM deployments need to be migrated to the new Loginapp UI.

  1. This roughly involves the following steps:
  2. Find out whether the latest version of Airlock IAM provides all features required to enable the migration of your deployment.
  3. Reconfigure the new Loginapp UI using flow features.
    This step involves analyzing the features of the JSP-Loginapp that are currently in use in your setup. Re-configuring them in the new Loginapp UI with flow features.
  4. There is no exact 1:1 mapping from (old) JSP-Loginapp to (new) Loginapp UI features and there will be no automatic migration.

  5. Re-do the customization (layout, design, etc.) of using the Design Kit for the Loginapp UI.
  6. Client applications relying on the JSP-Loginapp's web-frontend as API (HTML screen scraping, structure, order, ids, class names, etc. of elements) will fail.

    Such clients must be rewritten to use the Loginapp REST API instead.

  7. Test the configured Loginapp features. Be especially careful to test the interaction with other systems.