Release Notes / Customer Information

SR-Matterhorn 08.02.2026

Status: Final (02.02.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.


Launch date
  • REF:      ⇨ 09.12.2025 ↴
    ⚒ Regression testing ❌❎ ✉➔ eIAM ⚒✅
  • ABN:    ⇨ 14.01.2026 ↴
    ⚒ Regression testing ❌❎ ✉➔ eIAM ⚒✅
  • PROD:  ⇨ 08.02.2026 ↴
    Sunday ⚒ Final Inspection ❎❎ ✉➔ eIAM
Changes - Innovations
  • FED-LOGIN - Passwordless - Preparation
  • FED-LOGIN - Management of login methods without mandatory smartcard use
  • CH2A-Wizard - Improved user information for BYOI users
  • eIAM-MyAccount on Oblique
  • eIAM-AdminPortal on Oblique
  • Change of method for identity verification in AGOV for federal administration applications
  • eIAM-MyAccount - Removal of Single Sign-On (SSO)

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 - Passwordless - Preparation

FED-LOGIN is the primary identity provider (login method) used by employees of the Federal Administration and the cantons. In addition to login with smartcard and automatic login with Federal Administration office automation devices (Active Directory Single Sign-On), FED-LOGIN also supports complementary login methods. In addition to the modern and secure complementary login methods «FED-LOGIN Access App» for Apple iOS and Google Android devices and physical security keys (FIDO2), other login methods based on a password and a second factor were also supported in the past.

These login methods that use a password as the first factor will no longer be supported by FED-LOGIN with the «Mönch» release (production on 10 May 2026). The affected login methods include:

  • Password and mTAN (SMS code)
  • Password and one-time passcode (generated by an authenticator app such as Microsoft or Google Authenticator)
  • Password and Mobile ID
In this eIAM «Matterhorn» release, registration of these login methods for FED-LOGIN accounts will no longer be offered in eIAM-MyAccount as a preparatory step. Additionally, users logging in to FED-LOGIN using password-based login methods will be informed that these methods can no longer be used after 10 May 2026. Users are advised to proactively register and use the FED-LOGIN Access App and/or a security key (FIDO2) via self-service in eIAM-MyAccount. For users who do not have a smartcard, it is mandatory before 10 May 2026 to register login methods that continue to be supported for their FED-LOGIN account. Otherwise, they will no longer be able to log in to FED-LOGIN at the «high» level and their FED-LOGIN account will need to be reactivated through support processes. Including a re-verification of identity, to be carried out at the user's expense. Users equipped with a smartcard can continue (also after 10 May 2026) to register supported login methods in eIAM-MyAccount.

FED-LOGIN - Management of login methods without mandatory smartcard use

Until the «Matterhorn» release, individuals equipped with a smartcard from the federal administration (SG-PKI) were required to log in using the smartcard in order to manage (register/delete) their FED-LOGIN login methods in eIAM-MyAccount. Individuals not equipped with a smartcard (totally smartcardless) were able to log in using a «high» level login method (FED-LOGIN Access App, security key (FIDO2), or Mobile ID) and manage their login methods. As of the «Matterhorn» release, managing FED-LOGIN login methods in eIAM-MyAccount is generally possible using a «high» level login. Regardless of whether the person is equipped with a smartcard. This change allows all FED-LOGIN users to manage their login methods even on devices where the smartcard cannot be used. It is of course required that a «high» level login method is already registered for the FED-LOGIN account.

CH2A-Wizard - Improved user information for BYOI users

Users who access eIAM for the first time with their AGOV login are automatically recognized and have the option to replace an existing CH-LOGIN with their AGOV login, allowing them to retain all previously assigned permissions in applications under their AGOV login. The original CH-LOGIN is deleted after this process and can no longer be used. A small number of CH-LOGIN users have additionally linked their CH-LOGIN to a so-called BYOI (Bring Your Own Identity) identity, such as Genève-ID or Switch edu-ID. Until now, these users were informed that they would no longer be able to use their CH-LOGIN after upgrading to AGOV login. However, the explicit information that the BYOI identity would also no longer be usable was missing. This led some users to believe, after upgrading to AGOV login, that they could continue using their BYOI identity. Starting with the Matterhorn release, users in this situation will be informed that after upgrading to AGOV login, they can only use AGOV login and that both their CH-LOGIN and the link to their BYOI identity have been deleted.

eIAM-MyAccount on Oblique

The self-service portal eIAM-MyAccount allows users with CH-LOGIN and FED-LOGIN accounts to manage their login methods. For CH-LOGIN accounts, personal information can also be managed. With the «Matterhorn» release, eIAM-MyAccount will use Oblique, the standard design system for digital applications of the Swiss Confederation. This will change the design of eIAM-MyAccount. However, nothing will change functionally for users.

eIAM-AdminPortal on Oblique

The eIAM AdminPortal is used for the (delegated) management of authorizations in eIAM. With the «Matterhorn» release, the AdminPortal will use Oblique, the standard design system for digital applications of the Swiss Confederation. This will change the design of the AdminPortal. However, functionally, nothing will change for administrators.

Change of method for identity verification in AGOV for federal administration applications

Until now, the identity verification procedure with video identification has been used for verifying AGOV identities employed within the Federal Administration. In AGOV, the previous identity verification procedure with the name «Video identification (IDnow)» is being replaced by the procedure «ID/passport verification online». In contrast to the previous procedure «Video identification (IDnow)», the new procedure «ID/passport verification online» no longer depends on the availability of a human agent who performs the identity verification in real time and is therefore bound to defined opening hours. The new procedure «ID/passport verification online» can be carried out entirely without online interaction with an agent. The verification process is subsequently reviewed by a human agent, who approves or rejects it. This means that identity verification is no longer tied to fixed opening hours, can be performed at any time without waiting times, and can also be offered at a lower cost. Since all stages (REF/ABN/PROD) of eIAM use the productive AGOV environment, the switch of the identity verification method will take place with the release «Matterhorn» at the time of the rollout of the release «Matterhorn» in production.

eIAM-MyAccount - Removal of Single Sign-On (SSO)

As previously communicated in the release notes of the «Liskamm» release and reiterated in the release notes of the «Ludwigshöhe» release, the Single Sign-On functionality for accessing eIAM-MyAccount will be discontinued with the «Matterhorn» release.

In the past, self-administration for users in eIAM was possible through a Single Sign-On between the login to the business application and the login to the self-administration portal «MyAccount» of eIAM. Applications were able to offer users a link to MyAccount that did not require an additional login. This SSO redirect from the business application to MyAccount will no longer be offered from the «Matterhorn» release onward. On the one hand, the functionality is not compatible with the new eIAM integration patterns. On the other hand, it is no longer considered appropriate from a security perspective. The SSO functionality will no longer be available as of the eIAM «Matterhorn» release. Applications were previously asked to completely remove this feature with the redirect to MyAccount or to adjust it so that a new browser window directly opens the URL of eIAM MyAccount in the respective environment (REFERENCE, ACCEPTANCE, PRODUCTION). The user will then be prompted to log in. This ensures that the subject using eIAM-MyAccount is in fact the rightful owner of the identity—even if the user’s device has been left unattended for an extended period.


Environment URL
PRODUCTION https://www.myaccount.eiam.admin.ch
ACCEPTANCE https://www.myaccount-a.eiam.admin.ch
REFERENCE https://www.myaccount-r.eiam.admin.ch
Table with the URLs to be used to call up eIAM MyAccount.