Release Notes / Customer Information

>>> Freiburger 19. June 2022 <<<

Status: Finale Version


The Release Notes (RN) report on the enhancements, as well as new functionalities and changes to the eIAM Services as per the Roadmap DTI.

Please note that deadlines for the completion of documentation and concepts usually refer to the end of a release period and have nothing to do with the individual release dates (release dates) for functionalities.]

Release-dates / Changes Innovations


REF: 19 April 2022  <Tests!> ABN: 4 May 2022  <Tests!>  PROD: 19 June 2022
  • eIAM is switching to FED-LOGIN 2.0
  • CH-LOGIN IdP has been GUI technically revised
    • BYOI IdP's are now located at the bottom of the entry page
    • CH-LOGIN screens slightly revised in part
  • Cluster Release. Product Update of the Suite
    • Application-specific onboarding mail template
    • New icons in MyAccount
  • Consistency Checker
    • The Consistency Checker (CC) supports consistency of data in eIAM.
  • Access Request
    • New mandatory fields: Last Name, First Name and Phone Number
  • Password Reset
    • Password Reset new with mTAN instead of security questions (to reduce support requests)

Process and expectations for SR rollouts

In order to be able to guarantee the stable and secure productive eIAM service, we require meaningful regression tests of the applications in the REF and ABN instances until the SR rollout to PRODUCTION. You have at least 14 days per stage to do this. Please plan your test activities early in these periods so that any bugfix releases can be made in good time.

These release notes will help you to plan the regression tests in relation to the eIAM functionalities you use and will also serve as a source of information for your end customer communication. Please note that the final version of the release notes with all necessary details will be delivered shortly before the productive installation.

Important
If you encounter problems during your regression tests, please inform our testing team immediately at: Testing-eiam@bit.admin.ch. Our colleagues will take your input, check it and consolidate it. We would like to thank you for your important assistance and support in order to maintain and further improve the high quality standard of the service releases!

eIAM contact person

If you have any questions or concerns about eIAM, ePortal or PAMS you can contact the following offices or persons;

eIAM contact points
×

Release Notes

FED-LOGIN 2.0

The rollout of FED-LOGIN 2.0 was introduced with SR Gamaret on 20 March 2022 and has been available to most applications since then.

Since it is planned to scale back the existing IdP-Cert, IdP-Kerb and FED-LOGIN (old) in the course of 2022, we must plan and carry out the migration to FED-LOGIN 2.0 together with those responsible for the specialist applications. This can be done as part of a future configuration or services release.

There is currently still a problem with MVDI access via FED-LOGIN 2.0. The user gets an error message that the smartcard cannot be read before he can log in. The user can close this error message or wait until it disappears. For the login, the button "alternative login" must then be selected in order to carry out the login, e.g. with Mobile ID. The functionality is not affected in any way.

Error message that the smart card cannot be read.
Error message

CH-LOGIN and BYOI

The CH-LOGIN IdP was technically revised GUI. For example, the CH-LOGIN entry page has been revised.
Picture of the CH-LOGIN IdP GUI, which has been redesigned.
CH-LOGIN IdP


The BYOI IdP's are now located at the bottom of the entry page.
Representation of the BYOI IdP's
BYOI IdP’s


In addition to the entry page, some of the other CH-LOGIN screens have also been slightly revised to make navigation easier for the end user.

Cluster Release

With the SR Freiburger, various software components are also brought up to date (product update of the Suite). The IDM component is also updated. By means of a mouse-over function the tooltip is displayed and thus the function behind the icon can be derived for the moment.

Example

Image of the IDM component
IDM component

eIAM adminPortal

Application-specific onboarding mail template

The onboarding function in Delegate Management has been extended. Previously, there was only one onboarding mail per client. Now, one onboarding mail can be created per application. The onboarding mail can be conveniently edited via the editor in Delegate Management and is available in all four supported languages (DE, FR, IT, EN).

The onboarding e-mail can be edited in the admin portal under Application management -> Client -> Onboarding e-mail if you are authorised for this module.

Application-specific onboarding e-mail template
Onboarding e-mail template


New icons in MyAccount

With the adjustments to the CH-LOGIN, the new icons in the MyAccount have also been added.

Display of the new icons in MyAccount.
Icons in MyAccount

Consistency Checker

The Consistency Checker (CC) supports the consistency of data in eIAM. It synchronises changes between the federated identity and the identity references in the access client. The CC is introduced with this release, but initially only identities that run through the new identification process (VIPS) are synchronised. For these identities, consistency is ensured and the attributes "name, first name, e-mail, status and source system" are synchronised. In the next release of Diolinoir, this synchronisation can be adopted for all identity references in the AccessClient via whitelisting. This is the recommended setting for all Access clients.

For more detailed information, see the following

Consistency-Checker (Enforcer)

Access Request

The Access Request component, which is responsible for access requests to specialist applications, has been modified. The following fields are now mandatory fields: Surname, first name and telephone number.]
Figure Access Request with mandatory fields: last name, first name and telephone number
Mandatory fields: last name, first name and telephone number

The responsible GKA receives an e-mail from the user with the information filled in the Access Request form. In the event of a support case, the telephone number can be used as contact information.

Password Reset

Currently, to reset the CH-LOGIN password, users must answer the security questions they set. This results in a high number of failed password resets and subsequently many support cases. Asking security questions for a password reset is a rather unusual procedure. Therefore, this step has been removed from the password reset process. The second factor (e.g. mTAN) is now requested if one has been stored and no more security questions.