use login type configuration from ICM instead of hard coded type 'email'

[shauke]

Is your feature request related to a problem? If yes, please describe it.

ICM provides two options for user registration with the email address or with a chosen username. Currently the PWA is prepared to handle both ways but by default the registration and login are hard coded to use email (see src\app\core\configurations\injection-keys.ts).

/**
 * If 'username' login name is used for registration, if 'email' the email is used as login name (default: 'email')
 */
export const USER_REGISTRATION_LOGIN_TYPE = new InjectionToken<string>('userRegistrationLoginType', {
  factory: () => 'email',
});

Describe the desired solution.

Currently the ICM configurations REST call does not provide the information which login type is configured in the ICM backoffice. As soon as this is fixed the PWA needs to be adapted to handle both ways dynamically in accordance with the ICM configuration.

The login with username is not fully supported by the pwa, yet. Only the login page is showing the username. The registration page, the profile pages and maybe some other components have to be adapted, too.

Provide additional context.

AB#71466 REST: Preference LoginType not provided by GET /configurations call

AB#71849

[shauke]

This is now available (at least in 7.10.36.0) and can be implemented.

[Thomas-Bergmann]

The REST-client (PWA) doesn't need to care about the preference "UserRegistrationLoginType" at login. Only for registration and update profile. The type can improve the UI. In case of "email" both fields "login" and "email" can be displayed as one.
The ICM uses the "login", always.