Release Notes / Customer Information

SR-Nordend 15.11.2026

Status: working version (18.09.2026)
The Release Notes (RN) report on the enhancements, as well as new functionalities and changes to the eIAM Services as per the Roadmap FCh-DTI. Please direct your questions about the release to
Please note that dates 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

   REF ⇨ 22.09.2026 ↴
   Customer regression tests

   ABN ⇨ 28.10.2026 ↴
   Customer regression tests

   PROD ⇨ 15.11.2026
   Sunday – Final acceptance by customers


Changes - Innovations
  • FED-LOGIN - New frontend
  • MyAccount - Removal of the «Home» tab
  • New role model in eIAM nevisIdm
  • New software versions for various eIAM components
Breaking Changes
  • Important advance notice for the «Obergabelhorn» release
    Reduction of attributes in eIAM tokens
    • What will happen with the «Obergabelhorn» release
    • Application owners - Potential impacts on your Relying Parties (applications)
    • Application owners - Your role BEFORE the «Obergabelhorn» release dates
    • Application owners - Your role AFTER the «Obergabelhorn» release dates
    • Questions and support

Regression testing by eIAM customers

Your cooperation is necessary and very important. In the last releases, we had problems in the higher operating environments (ABN, PROD) only where applications had not carried out their regression tests in advance on REF and/or ABN. These are unnecessary problems which we can avoid together. We count on your support here. It is important that you carry out your regression tests carefully and report any problems to the testing team promptly and in a qualified manner.

Process and expectations for SR introductions

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. Normally you have 10 working days at your disposal for this. Please note that in the first 2 days after installation you can benefit from an Early Live Support Team that will assist you promptly in the case of problems.

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
Let us know your release test results (positive or negative) via Feedback form customer regression tests. (only accessible from the Federal Administration network) so that any service release corrections can be made in good time.

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
×

Changes - Innovations

FED-LOGIN - New frontend

Whenever users use their FED-LOGIN identity to access Federal Administration resources integrated into eIAM and the login method requires interaction with the users, they use the FED-LOGIN frontend. This is the case, for example, when authenticating with the FED-LOGIN Access App or with a security key. The FED-LOGIN identity provider has been completely redesigned and now provides users with a modern frontend implemented as a Single Page Application. This offers users the following benefits:
  • Immediate response: As the application is loaded only once, the interface responds instantly when users click on other menus or settings, without any noticeable delay.
  • No full-page reload: When navigating, complete web pages no longer need to be reloaded from the server.
  • Optimised for mobile use: Reduced data traffic. After the initial loading during login, complete web pages are no longer transferred.
In addition, the use of a modern architecture and the Federal Administration’s standard Oblique framework significantly improves the maintainability, accessibility and future extensibility of FED-LOGIN.

MyAccount - Removal of the «Home» tab

In eIAM MyAccount, the «Home» tab will no longer be available from the Nordend release onwards. When accessing eIAM MyAccount, users will now be taken directly to the «Profile» tab, where they can find their personal data.

Background: Until now, the eIAM self-administration portal «MyAccount» has provided users with a «Home» tab. The original idea behind this functionality was to allow users to find, in one central location, all applications for which they have permissions in eIAM and to launch the relevant application directly from there. It has become apparent that users make very little use of this functionality. At the same time, this functionality could only display applications whose authorisation management was handled directly within eIAM. For applications that use eIAM solely for authentication, eIAM does not have information indicating whether a person is authorised to use the respective application. As a result, only some of the applications available to users could be displayed, which increasingly led to users being unable to find significant parts of the applications available to them in MyAccount.

New role model in eIAM nevisIdm

The eIAM IDM system manages the permissions required to administer users, their profiles and their authorisations. A person’s administrative permissions within the IDM system are controlled on the one hand through authorisation roles (what the person is allowed to do) and on the other hand through data spaces (on which objects the person is allowed to perform these actions). In the new role model, the assignment of rights to roles has been fundamentally revised. Existing roles such as GKA and BVA now have the correct scope. Assigning additional roles to complete the required set of rights is no longer necessary. This has also made it possible to significantly reduce the number of IDM roles and eliminate redundancies. For governance reasons, roles for user administration are generally assigned by eIAM Operations or by persons delegated by eIAM Operations as GKD (overall service coordinators). As a general rule, a GKA (overall office coordinator) should only assign the BVA role (application authorisation administrator). Details on role assignment and the individual roles can be found under IDM Roles & Access Assignments . This change affects administrators, support staff and technical users with access to the IDM system.

Please note that the rollout of the new role model deliberately takes place one week before the actual release date of the Nordend release. This is intended to separate the migration of permissions from the release itself. The rollout dates for the new role model are as follows:

REF: 15.09.2026, 13:00 (CET)

ABN: 21.10.2026, 13:00 (CET)

PROD: 08.11.2026, 13:00 (CET)

Please report any problems to eIAM Operations (eIAM-Operations@bit.admin.ch).

New software versions for various eIAM components

As part of the regular life cycle and to ensure the functionality, stability and security of the eIAM service, various eIAM components are being updated to the latest software versions.

Breaking Changes

None for the «Nordend» release.

Important advance notice for the «Obergabelhorn» release
Reduction of attributes in eIAM tokens

As part of the implementation of the principles of «Privacy by Design» and data minimisation, the standard attribute sets of the tokens issued by eIAM to Relying Parties will be adjusted. The aim is to ensure that Relying Parties receive from eIAM only those attributes that they actually need for their functions. In short: as little as possible, as much as necessary. With the «Obergabelhorn» release, the standard attribute sets for both SAML 2.0 and OIDC federations will therefore be reduced to a minimum set of attributes. This change affects both new integrations with eIAM and existing eIAM integrations. We would therefore like to inform you at this stage about the process for this future change.

What will happen with the «Obergabelhorn» release
×

With the future «Obergabelhorn» release REF 15.12.2026, ABN 27.01.2027, PROD 14.02.2027 (please note: this change will not be introduced with the current Nordend release), the standard attribute set (claims) in eIAM tokens will be reduced. From the «Obergabelhorn» release onwards, the following attributes will be delivered by default in the eIAM token to the Relying Party:

Federations with:

Please note: Additional attributes that you have explicitly ordered via the eIAM dossier are not affected by this change. They will continue to be included in the token after the change.

Application owners - Potential impacts on your Relying Parties (applications)
×

Your Relying Party (application) receives tokens issued by eIAM in which some attributes that were present before the change will no longer be available. Possible impacts on your application include:
  • Login to your application may no longer be possible
  • Functions within your application may no longer work as expected because required information about the user or their authorisations is missing.

Application owners - Your role BEFORE the «Obergabelhorn» release dates
×


Application owners - Your role AFTER the «Obergabelhorn» release dates
×

  • As usual, you must carry out regression tests for your application immediately after the eIAM release, both in pre-production (REF/ABN) and in production (PROD).
  • Report regressions as usual via the established Feedback form customer regression tests. as part of eIAM Early Live Support (ELS).

Questions and support
×

If you have any questions about the reduction of attributes in eIAM tokens or require support, please contact eIAM-Integrations@bit.admin.ch at any time.