Loginapp migration - how to migrate?

Please consider the following recommendation when approaching the migration from the old JSP-Loginapp to the new Loginapp REST UI.

1. Managing expectations - What to expect?

The migration to the new Loginapp involves analyzing your current deployment, carefully validating whether and how all requirements can be met, and implementing it with the new Loginapp.

  • There is no automated migration from the old to the new Loginapp.
  • Some features of the JSP-Loginapp are no longer available in the new Loginapp. Refer to the list of discontinued features linked below.
  • There is no exact 1:1 mapping of old and new Loginapp features.
    • The UI customizing must be redone due to the different technological approaches.
    • Features may need to be configured in a new way using flow concepts.
    • The user experience may not exactly be the same as before in all cases.

Depending on the complexity of the migration, the effort required can vary greatly. The values in the following table are for orientation only and not binding.



Minimum effort in PD*


  • Simple authentication flow for one application
  • Few requirements on UI customizing
  • No self-services



  • Some applications with moderately complex authentication flow
  • Some self-service
  • No complex flows.
  • Moderate requirements on UI customizing
  • Assumption: all features are available in IAM



  • Many applications with complex ID propagation
  • Complex flows
  • Introduction of new flows (compared to old Loginapp configuration)
  • High requirements on UI customizing

> 20


PD = person-days

2. Conceptual phase

We recommend creating a kind of inventory of what was used in the old Loginapp. It could include the following information:

  • What use-cases were covered?
  • Which use-cases are still relevant?
  • Is it possible and worth it to rediscuss and reshape requirements with business representatives?
  • Identify customizations (custom code, customized JSPs, custom text elements)

Once you know what features have to be migrated, check whether all features are (already) available in the new Loginapp.

The documents linked at the bottom of the page may help to accomplish this task.

  • Design flow usage and how to implement non-flow features.
  • Check flows for adequate customer journey and security.

3. Implementation

For the implementation of the migration we roughly see the following steps:

  • Configure the Loginapp REST API (flows and other features).
  • Many basic configuration settings such as database, directory settings, the configuration of connected systems, password policies, etc. can be reused in the new configuration.

  • Configure the Loginapp REST UI (web UI specific configuration). The configured flows and UI settings can be fully tested with the product's standard look and feel.
  • Customize the look and feel of the UI. With the UI SDK, this can be done independently of the above.