AGOV Release Notes

Upcoming releases

AGOV 1.18 | Planned release date: 16.12.2026 | Name: Vanellus

AGOV 1.17 | Planned release date: 21.10.2026 | Name: Athene

AGOV 1.16 | Planned release date: 29.07.2026 | Name: Larus

AGOV 1.15 | Planned release date: 22.04.2026 | Name: Cuculus

Video summary (not public) →

Past releases

AGOV 1.14 | Release date: 28.01.2026 | Name: Perdix

Video summary (not public) →

Detailed release notes
New features

• Recovery code removal during registration
  • Recovery code will no longer be issued during registration of a new account.
    
  • Registration of a mobile phone number for easy account recovery remains optional.
    
  • The recovery code section including status and generation of a new recovery code option will be removed from AGOV me.
    
  • IMPORTANT: Users that still have access to a valid recovery code, will continue to be able to use it for account recovery purposes.
    
  • No changes in the recovery process.
    
    • Various account recovery options continue to be supported.
      
    • Users with a phone number linked to their account can recover access via SMS. A new recovery code is generated during the process and can be used for future recovery cases.
• Document upload in support tickets
  • Supporting documents (attachments) can now be provided when creating a support ticket via AGOV Help.
    
  • Document size limit is set to 3 MB and users will be be able to upload up to 5 files.

• Session timeout increase to 20 minutes (IdP).
  
• Removal of email address verified label in AGOV me.
  
• Several smaller bug fixes.
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.13 | Release date: 17.12.2025 | Name: Chloris

Detailed release notes
Bug fixes / Improvements

• Minor accessibility improvements for screen reader compatibility.
  
• Address suggestion now supports entries that begin with lowercase letters.
  
• Enhanced searchability in TreeSelectComponent.
  
• Revised text content for OBL and BmID letters.
  
• Fixed stepper navigation in AGOV Help component.
  
• Slightly adapted ZAS integration rules to include birth names when available in the ZAS database.
  
• Several smaller bug fixes.

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.12.1 | Release date: 12.11.2025 | Name: Monticola Saxatilis

Detailed release notes
Bug fixes / Improvements

• In the Recovery Cascade flow, since 19.02.2025, users of self-registered AGOV accounts (AGOVaq 100) have been sequentially offered various options for account recovery. The final option in the cascade, used only if all other methods fail, is the online submission of an ID document via the company Intrum, at the quality level required for QES according to ZertES.
  
• The implementation of this Intrum service under ZertES is changing as follows:
  
  • Previously: ID and video selfie upload combined with a live video call involving a human agent.
    
  • Now: ID and video selfie upload are done in self-service mode; a human agent reviews the submitted materials afterwards. AGOV customer no longer needs to participate in a video call.
    
• Identity verification quality:
  
  • Remains unchanged; still at the QES level as per ZertES.
    
• Improvements:
  
  • no online waiting time for AGOV customers
    
  • no video call required
    

• Relevant change for Application Owners
  
  • Change in the identity verification flow for AGOVaq100 accounts recovery
    
  • Recovery for accounts with an AGOVaq-level higher than 100 remains unchanged.
    

AGOV 1.12 | Release date: 15.10.2025 | Name: Monticola

• Encrypted payload
  
  • It is now possible to request that the tokens issued by AGOV IdP are encrypted (SAML Assertion, ID-Token, and UserInfo).
    
  • This feature is available upon special request, restricted to Application Owners.
    

• Success and warning notifications will auto-dismiss after 5 and 10 seconds respectively. Error messages will stay visible until dismissed manually.
  
• Added keyboard input types for improved mobile user experience.
  
• Rollout of a new link standardization concept.
  
• Minor design change for the error pages.
  
• Switzerland will appear first in all relevant dropdowns throughout AGOV (typing logic will not be impacted).
  
• Several smaller bug fixes.
  

• Breaking change to the IdP specification
  
  • Romansh (RM) language can now also appear in the tokens delivered to the relying parties, if a user sets RM as language.
    
  • A new attribute/claim conversationId is part of the tokens (ID Token, SAML Assertion). It is a unique technical identifier which can be used to trace issuance of the tokens in the AGOV infrastructure.
    

AGOV 1.11.1 | Release date: 17.09.2025 | Name: Coracias Hotfix

Detailed release notes
Breaking changes / Relevant changes for Application Owners

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures
    

AGOV 1.11 | Release date: 13.08.2025 | Name: Coracias

Detailed release notes
New features

• Introduction of Romansh
  
  • AGOV will support all official CH languages.
    
  • At the moment it is not possible to go through a video identification in Romansh, therefore, VIPS process will default to browser language.
    
• Changes in the BmID process
  
  • Simplified process with quality increase and reduction of paper waste.
    
  • Data from the identification document will be ''read'' with the support of an App (MRZ scan).
    
  • Users will continue to have the option of using an ID card, passport or the residence permit to identify themselves.
    
  • Very old paper printed foreign IDs and paper based Swiss residence permits will not be supported, because they lack the machine-readable zone and, as a result, the data quality cannot be assured.
    
  • Stricter validation rules for security purposes.

• Validity of AGOVaq200 accounts was extended to 10 years, including migration of existing accounts.
  
• Accessibility improvement for the QR code scan.
  
• A new counter option was introduced for particular users (Remote Identification Officer).
  
• Numbers are now allowed in the name field of AGOV me, for covering specific edge cases. This change applies strictly for AGOVaq100 accounts.
  
• The login mask design has undergone minor modifications.
  
•  "Generate recovery code" was eliminated for AGOVaq100 accounts, if a recovery is initiated and identification is successfully finalized.
  
• Several smaller bug fixes.

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.10.1 | Release date: 25.06.2025 | Name: Alcedo Hotfix

Detailed release notes
Breaking changes / Relevant changes for Application Owners

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures
    

AGOV 1.10 | Release date: 14.05.2025 | Name: Alcedo

Detailed release notes
New features

• New menu entry: Where is my application
  
  • Users will be informed that a government application cannot be directly accessed via AGOV me.
    
  • Additional information is available in AGOV Help.
    

• Increased amount of allowed and supported characters in ticket form description field.
  
• Improved the application selection list, while maintaining also type and search function.
  
• Improved the error messages in the description field of the ticket form, to provide more clarity to the users.
  
• GUI extension to provide the ticket ID to the user; mail flow will not undergo any modifications.
  
• Swiss Post consignment tracking API change.
  
• Several smaller bug fixes.
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.9 | Release date: 19.03.2025 | Name: Lagopus

Detailed release notes

Bug fixes / Improvements

• Swiss Residence Permit is now allowed for BmID identity verification in edge cases.
  
• AGOV access app is now supporting up to 10 registered accounts.
  

• Potential Breaking Change to the IDP Specification
  
  • AGOV IdP: For OIDC clients the claim "address.formatted" will not contain the name of the user anymore
    
    • Applications which use this field must adapt accordingly. For details, please consult the AGOV Identity Provider Interface V1.9 (15.10.2025) - Language: English
      
  Note: The change only affects OIDC clients which use the address scope. Other applications are not affected.
  

AGOV 1.8.1 | Release date: 19.02.2025 | Name: Pinicola Plus

Detailed release notes
New features

• Account recovery process changes
  
  • The account recovery for AGOVaq100 accounts now follows a sequential approach:
    
    1. Recovery code entry
    
    • User is asked to provide their recovery code.
      2. SMS recovery (if recovery code unavailable)
      
    • System checks if a mobile phone number is registered for the respective account.
      
    • If available, recovery via SMS is automatically triggered.
      3. OBL (if no phone number stored)
      
    • User can complete the account recovery using OBL.
      4. ID document (if OBL unavailable)
      
    • Available when OBL is not a viable option (e.g., address outside of Switzerland)
      
    • Recovery can be completed with the online submission of an ID document.
      
  • Recovery for accounts higher than AGOVaq100
    
    • A new verification is required.
      
    • The verification method can differ from the initial verification method
      
    • Applications owners must define which verification methods are permitted.
      
  • Login procedure changes
    
    • A temporary notification screen has been added to encourage users to add their mobile phone number.
      
    • Displayed after login for users that do not have a mobile phone number associated to their account.
      
    • Rationale: facilitation of an easier account recovery procedure in the future
      

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.8 | Release date: 08.01.2025 | Name: Pinicola

Detailed release notes
New features

• Change of attribute length
  
  • The attribute email will be shortened from 300 to 255 characters for SAML and OIDC integrations.
    
• Change to the verification for AGOV counter
  
  • Removal of the e-mail address from the verification process using AGOV counter
    
  • New: The counter agent will only have to enter the verification code
    
• Change to the registration process
  
  • Numbers have shown that a lot of users lose their recovery codes.
    
  • Users are now forced to manually write down or download the recovery code.
    
  • Entry of the recovery code one step later is required, to ensure that the user did not skip the recovery code.
    
• Added a banner that login-factors shall not be shared with others during account registration and login factor registration in AGOV me.
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.7.2 | Date: 18.12.2024 | Name: Zapornia Hotfix

Detailed release notes
New features

• Registration flow changes
  
  • A new step within the registration is introduced, which asks the user to enter his or her mobile phone number for recovery purposes.
    
  • This is a preparatory step to allow AGOV additional recovery options.
    
  • Additional recovery options will be introduced in the upcoming Release 1.8.1 "Pinicola" Plus.
    

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.7.1 | Release date: 21.11.2024 | Name: Zapornia Hotfix

Detailed release notes
New features

• Revision of HaloITSM ticket entry form
  
  • A new form to enter support-tickets for endusers will be implemented.
    
  • Main goal is to make the support compliant to data protection laws.
    
    • No use of google reCAPTCHA
      
    • No use of Google Fonts
      

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures.
    

AGOV 1.7 | Release date: 13.11.2024 | Name: Zapornia

Detailed release notes
New features

• Change to login to AGOV me and registration
  
  • During registration users will now be informed that the AGOV access app will only function properly, if push-notifications are enabled.
    
  • During login to AGOV me users will now be informed that all of their Access Apps do not have push-notifications enabled
    
• Added new functionality with VIPS verifications
  
  • Changes done by the VIPS Agent will now be stored by AGOV
    
  • Due to the fact that the VideoIdentification is ZertES qualified, the following attributes may be changed by the agent:
    
    • First name
      
    • Last name
      
    • Birthdate
      
    • Nationality
      
    • Gender
      
  • Users will see the updated values in AGOV me, once the verification has been concluded.
    

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.6 | Release date: 25.09.2024 | Name: Sterna

Detailed release notes
New features

• Change to the BmID verification process
  
  • In addition to the ID check by the member of the Swiss Post the user must now also enter a verification code (similar to OBL).
    
  • Users will receive the code in form of a letter, which will only be handed over by the Member of the Swiss Post upon a successful ID / Passport check.
    
  • Users can only enter the code after the ID check has been completed.
    
  • Important: Users with an ongoing BmID verification started before the go-live date will be able to finish that verification without need of a verification code.
    
  • These are only changes in the user flow, there are no changes in the authentication quality (AGOVaq)
    
• Improved Verification method selection
  
  • Introducing the possibility to define if AGOV counter and Video Identification are available for users livings abroad -> To remove the dead-end for users living abroad trying to access an AGOVaq 200 application
    
    • Can be configured per integration in AGOV connect
      
  • Introducing the Verification Selection Questionnaire for AGOVaq 200 verifications
    
  • Improved the Verification Selection Questionnaire, so that only verification methods supporting the user’s selection are shown
    
    • Parameters are:
      
      • Does user live abroad or in Switzerland?
        
      • Nationality of the User
        
      • ID document types the user possesses
        
    • Depending on those answers, the fitting verification methods are shown
      
• Separating the list of nationalities and countries
  
  • Nationalities only lists possible nationalities -> previously also territories were listed as well
    
  • Countries (mostly for addresses) list all countries including their territories.
    
• AGOV view for L1 Support Agent
  
  • AGOV view is also now available for L1 support agents.
    
  • The dataset available through AGOV view for L1 support agents is reduced.
    
  • L1 support agents are currently not able to initiate a manual recovery.
    
• Switch from Google ReCaptcha to Friendly Captcha
  
  • All instances of Google ReCaptcha have been replaced with Friendly Captcha to improve data privacy
    
• Users are now requested to repeat their ID / Passport number
  
  • In order to prevent failed verification due to a typo in the ID / Passport number, users are now requested to repeat the ID / Passport number after entering it initially.
    

• Breaking Change to the IDP Specification
  
  • AGOV IdP: For OIDC clients there is a new attribute verificationMethod in the address claim. This provides information on the method used to verify the address (especially for AGOVaq300/400 accounts, the address verification may have a different quality). Further information in the updated version of the IdP specification: AGOV Identity Provider Interface
    Note: The change only affects OIDC clients that use the address scope. Other applications are not affected.
    

AGOV 1.5.9 | Release date: 14.08.2024 | Name: Apus cooki

Detailed release notes
Breaking changes / Relevant changes for Application Owners

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.5 | Release date: 10.07.2024 | Name: Apus

Detailed release notes
New features

• Introducing AGOV view for Support Agents (L2 only with this release)
  
  • Ability to set mustRecover role through AGOV view
    
  • Ability to see the state of the user's account in an easy overview
    
• New feature AGOV counter:
  
  • Ability to define a location specific text, which will be displayed to the user during location selection and on all invitation/confirmation documentation (screen, PDF and E-Mail)
    
    • Text can be defined in all currently supported languages.
      
    • Text will be added during set-up of the AGOV counter location. Can also be added / amended at a later date.
      
  • E-Mail sent out to account holders with all the information to visit the AGOV counter location (same information as on the PDF).
    

• Several bug fixes and improvements in regards to the stability of verifications.
  
• Visual improvements within the AGOV counter application.
  
• Misc. smaller bug fixes and improvements.
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.4.7 | Release date: 19.06.2024 | Name: Otus Scops

Detailed release notes
Bug fixes / Improvements

• Until now only DOMICILE_CERTIFIED addresses were accepted
  
  • Name of the person and the address are registered in that combination in the Swiss Post Database
    
• For AGOVaq Level 300 and 400 verifications also CERTIFIED addresses are now accepted with this change.
  
  • That means that we check that it is a valid address that exists. However the person might not be registered with the Swiss Post at that address.
    
• For AGOVaq Level 200 verifications nothing changes.
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification - Address is always delivered in the same way.
    
  • No changes to Authentication procedures
    

AGOV 1.4 | Release date: 05.06.2024 | Name: Otus

Detailed release notes
New features

• Introduction of user self-payment for Videoidentification
  
  • Ability to let users pay for their own verification
    
    • Feature should only be used if the legal framework governing the target application allows it.
      
    • These verifications will not be billed towards the application owner
      
• Introducing the possibility of configuring Videoidentification to be user self-payed instead of being billed towards the target application in AGOV connect
  
  • Feature should only be used if the legal framework governing the target application allows it.
    

• Fixed an issue that prevented users from using hardware-based Windows Hello as a security key.
  
  • Remedy for affected users is underway. Affected users should contact AGOV support via AGOV help by creating a ticket.
    
• Solved a logout issue on the AGOV canary page
  
• Overall improvement of stability of verification components and flows
  
• Bug fixing in the AGOV counter flows
  
• Some overall improvements to AGOV connect
  
  • Handling of integrations with status “draft”
    
  • Improve the naming scheme for certificates for SAML integrations
    
• Various smaller bug fixes and various smaller improvements
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.3 | Release date: 15.05.2024 | Name: Merops

Detailed release notes
New features

• AGOV connect application now available to integrate Applications with AGOV
  
  • Possibility to integrate SAML, OIDC Private and OIDC Public applications
    
  • Ability to see all integrations for a unit (where access has been granted)
    
  • Ability to see detail information of an integration
    
  • Ability to see the certificate validity for SAML applications in the detail view
    
  • Ability to delete and edit integrations
    
  • Ability to prepare integrations without setting them live (draft status)
    
  • Ability to prepare changes to integrations without setting them live (draft status for changes)
    
  • Ability to clone integrations (also with with the option of draft status)
    
  • Ability to define a user facing application name in English, German, French and Italian
    
  • Ability to define a user facing application logo in English, German, French and Italian
    
• Introduction of AGOV canary mode
  
  • Ability to set AGOV canary cookie to test unreleased versions of AGOV (canary mode will be used on Production later this year)
    
  • Ability to disable the AGOV canary cookie
    
  • Introduction of Indicator in Header to indicate if a canary cookie has been set
    
• Introduction of AGOV recovery questionnaire
  
  • New questionnaire to guide users before starting a recovery process, to determine if a recovery is really necessary
    

• Several security improvements (based on Bug Bounty findings)
  
• Several technical improvements in the user flows to further stabilise AGOV
  
• Several smaller bug fixes
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.2 | Release date: 03.04.2024 | Name: Spinus

• AGOV counter application now available to carry out verifications (AGOVaq300 and 400)
  
• Enabled applications to allow AGOV counter as a verification method for AGOVaq300 and AGOVaq400 verifications
  
• Users can carry out their verifications for AGOV counter (where available)
  
• Extended AGOV recovery flows with the option to carry out recovery with AGOV counter (for users with initial AGOV counter verification)
  

• Improve handling of Verifications and their pending states
  
• Improved displaying of verified data directly after verification
  
• Fixed issue regarding validity time range for AGOVaq400 accounts
  
• Several smaller bug fixes
  

• We are not expecting any breaking changes
  
  • No changes to IdP Specification
    
  • No changes to Authentication procedures
    

AGOV 1.1 | Release date: 06.03.2024 | Name: Falco

• Postal address verification also on AGOVaq300 and AGOVaq400, for addresses in Switzerland
  
• Blacklist for Software-FIDO keys
  
• Suppress postal address verification for non-CH postal addresses
  
• Change help link in the Nevis Apps Gear section: change display text and add imprint
  
• Implement findings of latest accessibility review
  
• Rework on IdP for branding for target applications
  
• Rework on existing translations
  
• Rework on recovery process where support is involved
  
• Add text about responsibility of control when registering additional login factors
  
• Add information in IdP Specification document
  
• Enhance statistics and logging
  

AGOV 1.0.23 | Release date: 07.02.2024 | Name: Serinus

• AGOV now supports (after AGOVaq100 and 200) the AGOV authentication qualities AGOVaq300 and 400 (verified identities with or without AHV number, according to the AGOV study. Existing applications are not affected by this functional expansion.
  
• Improvement: AGOV me now only displays the "AHV information" area if the AGOVaq level is 400 (we expect a reduction in support requests).
  
• Improvement: When registering an AGOV account, the timeout is set now to 10 minutes to confirm the email code instead of just 3 minutes, which was too short in certain cases.
  
• Correction: The designation of the third gender was changed to “No information”.
  
• Improvement: International telephone numbers can now be saved in AGOV me.
  
• Improvement: Name and logo of the requested application is displayed on the login page.
  

AGOV 1.0 | Release date: 15.12.2023 | Name: MVP-1.0

• Register AGOV login (AGOV access & FIDO)
  
• Verification aq200 inkl. CRQ 4a
  
• Recovery aq100 incl. CRQ 4f
  
• Recovery aq200
  
• Edit Data aq100
  
• Edit Data aq200
  
• Login aq100 (AGOV access & FIDO)
  
• Login aq200 (AGOV access & FIDO)
  
• Register AGOV access app
  
• Register FIDO-token
  
• Remove Login factor
  
• Accounting module (AGOV meter - CRQ 4b)
  
• AGOV access app
  
  • iOS App store
    
  • Google Play store
    
• Interfaces
  
  • SAML Interface
    
    • Metadata
      
    • Authentication Flow
      
    • Content Assertion
      
  • OIDC Interface
    
    • Discovery Data
      
    • Authentication Flow
      
    • Content ID Token
      
• Printing and delivery of OBL letters
  
• AGOV operations
  
  • Monitoring & Alarming
    
  • Incident Management Prozess
    
  • Problem Management Prozess
    
  • Service Management Prozess
    
  • Release Management Prozess
    
• AGOV help
  
  • App is up and running
    
  • App contains first knowledgebase entries
    
  • The ticket system is available to open a ticket, if the knowledgebase doesn't contain an appropriate entry
    
  • The ChatBot is up and running that guides the end users, first to the knowledgebase articles, and then to the self-service ticket system.
    

AGOV 0.9 | Release date: 01.11.2023 | Name: MVP-0.9

• Allows for self-registration.
  
• Allows for the identity verification process for AGOVaq200, if (and only if) the target application requests it.
  
• This address verification process includes the sending of a letter to an address within Switzerland.
  
• The step-up from AGOVaq100 (self-registered) to AGOVaq200 works if the target application requests it.
  
• Login works with both types of credentials (Betriebssysteme and Sicherheitsschlüssel).
  
• Target applications can connect through SAML
  
• Target applications can connect through OIDC
  
• All links in the AGOV modules resolve to the correct targets (in particular to the credential above and the help pages).
  
• The AGOV access app is publicly available in the Apple App store, world wide and in production.
  
• The AGOV access app is publicly available in the Google Play Store, world wide and in production.
  
• In both App-stores, searching for AGOV leads to the right access app.
  
• The PoC App is no longer visible in either store