Release Notes / Customer Information

SR-Nadelhorn 16.08.2026

Status: Final (20.07.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 ⇨ 23.06.2026 ↴
   Customer regression tests

   ABN ⇨ 22.07.2026 ↴
   Customer regression tests

   PROD ⇨ 16.08.2026
   Sunday – Final acceptance by customers


Changes - Innovations
  • FED-LOGIN totally Smartcardless
    • FED-LOGIN totally Smartcardless - New Onboarding Process
    • FED-LOGIN totally Smartcardless - Self-Service Recovery of Complementary Login Methods
    • FED-LOGIN totally Smartcardless - Retention of Complementary Login Methods
  • FED-LOGIN Access App – New version available from 29 July 2026 at 18:00 CET
  • MyAccount - Display of «Active Directory» as a Login Method for FED-LOGIN Identities
  • MyAccount – Display of «SSN (AHV) number» and «Date of Birth» for FED-LOGIN Identities
  • HIN Classic IdP Sector
  • New software version for various eIAM components
Breaking Changes
  • None

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 totally Smartcardless

Internal/external employees of the Federal Administration who are not to be equipped with a smartcard, but who nevertheless require FED-LOGIN authentication methods at the high assurance level (e.g., for accessing GEVER) or for use with mobile devices, can use FED-LOGIN totally Smartcardless for this purpose. The FED-LOGIN totally Smartcardless service ensures, on the one hand, that the person's identity is verified using appropriate processes and, on the other hand, that strong login methods (FED-LOGIN access app / security key) are linked to the owner of the FED-LOGIN identity via secure processes. In the eIAM Nadelhorn release, the service for FED-LOGIN totally Smartcardless users is being improved and expanded. You can find details in this chapter.

Please note that due to dependencies with documentation and user guidance, this functionality can only be rolled out in pre-production (REF/ABN) shortly before the go-live in production in August 2026. Until then, the existing solution for totally Smartcardless can continue to be used in all eIAM operating environments. Help on totally Smartcardless can be found here: Users without smartcard.

FED-LOGIN totally Smartcardless - New Onboarding Process

The onboarding process for totally Smartcardless has been redesigned. Previously, a proprietary solution was used to verify identity. This solution required a proprietary (chargeable) identity verification in every operating environment (PROD/ABN/REF) of eIAM for onboarding. Now, AGOV, the Swiss authorities' login service, will be used to verify the person's identity. Federal Administration employees can use their existing AGOV login to prove their identity and thus verify themselves as the rightful owner of the FED-LOGIN account. The prerequisite for using the AGOV login as proof of identity is a verified AGOV login (e.g., via Online ID/Passport verification)—ideally including a verified OASI (AHV) number. The use of the OASI number allows the person's identity to be uniquely recognized between AGOV and FED-LOGIN, even if the personal data stored in AGOV (first name(s), last name(s)) from the identity document differs slightly from the personal data originating from the Federal Administration's HR systems. If the person's OASI number is not verified in AGOV or has not been delivered to eIAM via the Federal Administration's HR processes, an attempt is made to match the person's identity between AGOV and eIAM FED-LOGIN using first name(s), last name(s), and date of birth. By the way, with the official availability of the Swiss e-ID, the use of the e-ID in AGOV for verification will automatically become possible as well. An additional, chargeable verification of the AGOV login is completely eliminated with the use of the Swiss e-ID.

Important Note:
The verified AGOV login used for totally Smartcardless can be registered to any email address. The email address of the AGOV login does not have to match the email address of the FED-LOGIN account.

FED-LOGIN totally Smartcardless - Self-Service Recovery of Complementary Login Methods

Previously, losing the complementary FED-LOGIN credential registered via totally Smartcardless meant that the totally Smartcardless user's FED-LOGIN account had to be reset via support processes. Following this, users had to undergo a complete, new onboarding process, including a new, chargeable identity verification. As of the Nadelhorn release, it is now possible for employees using FED-LOGIN totally Smartcardless to use their verified AGOV login for identity verification and manage (remove / register) credentials in MyAccount via self-service, without the help of the support organization—just as individuals with a smartcard can do by using their smartcard as a means of identity verification.

FED-LOGIN totally Smartcardless - Retention of Complementary Login Methods

Previously, if a user with FED-LOGIN totally Smartcardless was subsequently equipped with a smartcard, the complementary credentials (FED-LOGIN Access App / security key) registered via totally Smartcardless processes were revoked. If needed, these credentials had to be re-registered using the smartcard as proof of identity. Now, these login methods are retained even if a smartcard is subsequently issued. They can continue to be used by the user without interruption.

FED-LOGIN Access App – New version available from 29 July 2026 at 18:00 CET

The new version 4.0.0 of the FED-LOGIN Access App is available in the official Apple and Google app stores. Accessibility has been improved overall, including better keyboard navigation and enhanced screen reader support. This version also includes several bug fixes and visual improvements.

MyAccount - Display of «Active Directory» as a Login Method for FED-LOGIN Identities

Previously, the «Active Directory» login method was not displayed in eIAM MyAccount for FED-LOGIN identities. This could lead to confusion, especially for users without a smartcard, as they could successfully log in with FED-LOGIN but no usable login method was listed in MyAccount. Now, the «Active Directory» login method will also be displayed if it can be used by the user in FED-LOGIN.

MyAccount – Display of «SSN (AHV) number» and «Date of Birth» for FED-LOGIN Identities

Starting with the «Nadelhorn» release, the «SSN (AHV) number» and «Date of Birth» attributes will also be displayed in the «User Profile» tab of eIAM MyAccount for FED-LOGIN identities of internal and external employees. Displaying this additional information enables users of FED-LOGIN totally Smartcardless, in particular, to verify their personal data through self-service and, where necessary, request corrections.

Note:
These data originate from the Federal Administration’s HR systems and are maintained there. If a user’s data are incorrect, they must be corrected through the relevant HR processes. Users are requested to arrange any necessary corrections directly with their responsible HR organisation. The eIAM service has no influence on the quality of these data.

HIN Classic IdP Sector

For certain Federal Administration applications in the healthcare sector, electronic identities provided by the identity provider «HIN» can be used in eIAM. As HIN informed its customers in early July 2026 (see HIN Blog), several technical changes and migrations are being carried out as part of the renewal of HIN's infrastructure and its collaboration with ELCASecurity. Among other changes, the current HIN IdP will be replaced.

The eIAM service will establish the federation between the Federal Trust Broker (BTB) and the new HIN IdP on your behalf. For eIAM customers who use HIN identities for their applications, no action is required and nothing will change. The migration from the existing HIN IdP to the new HIN IdP will take place according to the following schedule.

Pre-production (REF/ABN): 22 July 2026, with the go-live of the «Nadelhorn» release in the ABN environment.

Production (PROD): 16 August 2026, with the go-live of the «Nadelhorn» release in the PROD environment.

New software version for various eIAM components

As part of lifecycle management and to ensure the functionality, security, and stability of eIAM, various eIAM components are being updated to the latest software version.

Breaking Changes

None