Frequently Asked Questions

Installing, uninstalling and starting the app

Which is the current version of AusweisApp2?

How do I install AusweisApp2?

Your update does not work or why is the predecessor version preserved despite the update? (Windows)

AusweisApp2 does not start on Mac OS X / macOS?

Can the Android app only be downloaded from Google Playstore (with a Google account)?

I will get a new smartphone, what do I have to consider in regard to AusweisApp2?

Virus scanner or firewall prevent functions of the AusweisApp2?

What does AusweisApp2 need to create firewall rules for?

How do I uninstall AusweisApp2 completely?

 

Supported systems, browsers and devices

Which operating systems are supported by AusweisApp2?

Which browsers can be used with AusweisApp2?

Why are Linux and Windows 10 mobile not supported by AusweisApp2?

Why does the AusweisApp2 not work on my iPad?

Which screenreaders can be used?

 

All about PIN

What are Transport PIN, CAN and PUK?

PIN forgotten or transport PIN incorrect - what to do?

How do I change my transport PIN / Error "Time exceeded"?

 

Online ID function

What is the online identification function?

Where can I use the online identification function?

How to use a smartphone or tablet for direct readout via NFC

 

Card readers and NFC function

Which card readers are supported by AusweisApp2?

Which mobile devices can be used for the Online Identification Function via NFC?

How to use a NFC-enabled device as a card reader (with another mobile device or a PC)

Is identification on mobile devies as secure as with a card reader?

 

Explanations of the NFC function

What is NFC?

Why do you need NFC for (mobile) use of the AusweisApp2?

Why does the online ID function not work even though contactless payment via NFC (Google Pay, Apple Pay etc.) works perfectly?

What is the challenge with extended length communication?

What is the challenge with the field strength of the NFC chip?

 

Problems and solutions

I encounter problems with my external card reader/ My card reader is not recognized

My smartphone does not recognize the online ID card

How do I achieve a stable connection between ID card and smartphone?

What does "scan ID" mean in the iOS version of AusweisApp2?

Why does the "Scan ID Card" process keeps failing with the iOS version?

Why can't the NFC interface in the iPhone SE and 6S (Plus) be used for the AusweisApp2?

Why can't I connect a normal card reader to a mobile device via micro USB?

Why does my Android mobile device report "No supported app for this NFC tag" or "Perform action with..." when putting ID and Smartphobe together, but AusweisApp2 is missing in the displayed list of applications?

Why does AusweisApp2 ask me to put on my ID card although no card reader is connected yet?

 

Providers

Which providers are available?

Why can't I find every provider in the provider overview?

Why aren't all providers available via smartphone?

Why do I get an error message in the browser from the service provider on Windows/ macOS?

Why do I get an error message after a successful identification process when I am redirected from AusweisApp2 to the service provider?

Contacting the support team

You did not find an answer to your question?

Our support team will be happy to help you!

E-mail: supportausweisappde

Phone: 0421 / 204 95 - 995 (local rate)

You can reach us from Monday to Friday from 9 am to 5 pm.

Which is the current version of AusweisApp2?

Currently, application version 1.22.2 is available to download. You can find the application version you have currently installed on your device in the menu item "Help" > "Version information".

How do I install AusweisApp2?

You can find installation instructions for AusweisApp2 under Windows here.

You can find installation instructions for AusweisApp2 under Mac OS here.

Your update does not work or why is the predecessor version preserved despite the update? (Windows)

When the updating process does not work on your computer, please go into the Windows control panel computer and uninstall the older version manually. After this is done, the already installed, current version can be opend.

AusweisApp2 does not start on Mac OS X / macOS?

The app is designed in such a way that it is not permanently visible in the foreground. That is why you will not find the program at the bottom in the dock bar, as is often the case, but at the top in the menu bar. To be able to authenticate, you first have to open the program. Now, in the second step, you can either call up a service via the provider list or start an authentication via the website of a service provider - the app then automatically appears in the foreground.

Can the Android app only be downloaded from Google Playstore (with a Google account)?

If you do not have a Google account or do not want to download the Android version of AusweisApp2 from Google Playstore for any other reason, you can send a request to our Support to be sent the apk file of AusweisApp2 for Android. You can then load this version directly to your device. The AusweisApp2 can also be downloaded from the open source platform GitHub. These versions can then be downloaded directly to your device.

Please note that in this case you will not receive any automatic updates. For this reason, we do not recommend this approach.

I will get a new smartphone, what do I have to consider in regard to AusweisApp2?

Since your data is read directly from the ID card each time and not stored on your smartphone, you only need to install AusweisApp2 on your new smartphone and can continue to use it as usual.

If you have used your smartphone as a card reader on a computer or tablet, you will have to pair the new smartphone with your device once again. 

If you have already used the online ID function on your old smartphone and have set a self-selected six-digit ID PIN, this will remain valid. The five-digit transport PIN, which you will find in your PIN letter, is only used once to assign a self-selected, six-digit PIN.

Virus scanner or firewall prevent functions of the AusweisApp2?

If you are using a firewall or virus scanner that differs from the default settings, it may be that the AusweisApp2 is blocked.
To be able to use the AusweisApp2 despite the settings you have made, you also have the option of entering an exception for the app.
If you need help with the settings, please contact our support.

What does AusweisApp2 need to create firewall rules for?

Firewall rules basically define which data traffic is permitted by a firewall. The AusweisApp2 installer offers the option of registering the required firewall rules in the Windows firewall for all the AusweisApp2 functions.

• For establishing a connection with the servers of the service providers.
• For using a smartphone as a card reader in the local network.

If the firewall rules are not registered, when the AusweisApp2 connects to a service provider, the user is asked once with a dialog in the Windows firewall to allow the outgoing data connections. However, the "Smartphone as card reader" function can only be used if the automatic firewall rules were created during installation.

How do I uninstall AusweisApp2 completely?

For Windows:

Uninstall AusweisApp2 via:
Start menu>Programs>AusweisApp2>Uninstall. This removes all files and the desktop icon of AusweisApp2 from your computer. For a complete removal you have to delete the following entries manually:

Registry entries:

  • Delete the complete folder Governikus GmbH & Co. KG
  • Delete the entries for AusweisApp2 under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run


NoScript settings in the Firefox browser:

  • Delete rule, if applicable


For Mac OS X:

Delete AusweisApp2 from the applications folder. This removes all files and the desktop icon of AusweisApp2 from your computer. For a complete removal you have to delete the following entries manually:

  • Delete the file "com.governikus-gmbh-co-kg.AusweisApp2.plist". This file is located in one of the following directories: "$HOME/Library/Preferences/" or "/Library/Preferences/".
  • Open the tab "Login Items" under "System Preferences" -> "Users & Groups" -> "Current User". Delete the entry "AusweisApp2" from the list.
  • NoScript settings in the Firefox browser: Delete rule, if applicable

Which operating systems are supported by AusweisApp2?

Android (5.0 or higehr), Windows (7 SP1 + 8.1 + 10), iOS (13.0 or higher), macOS (10.13 or higher)

Which browsers can be used with AusweisApp2?

Due to strict compliance with the corresponding technical guidelines of BSI (BSI TR-03124), the AusweisApp2 is browser-independent and supports all customary browsers. Within the scope of quality assurance we are testing the most customary browsers. On mobile systems, especially iOS, the respective browser used should be set as the default browser, otherwise misbehavior may occur. The release notes will give you more detailed informations.

Why are Linux and Windows 10 mobile not supported by AusweisApp2?

The development of AusweisApp2 has focused on the most widely used operating systems. The rule underlying the development states that the distribution of an operating system must reach at least 5% market share - this development is of course continuously monitored. Linux and Windows 10 mobile unfortunately do not currently reach the required market share.

However, the open source status of the software makes it possible to use and further develop the source code accordingly. You can find the source code on GitHub.

Why does the AusweisApp2 not work on my iPad?

First of all, unfortunately iPads do not have a (suitable) NFC interface, therefore you cannot use your iPad for direct reading. However, it is possible to use a smartphone (Android or iOS) as a card reader in conjunction with an iPad.

However, please note the following: With iOS 13, Apple has changed the Safari browser on iPads so that it opens all web pages in "desktop mode" by default. On the iPad, this has the consequence that the AusweisApp2 is no longer called correctly. Safari then displays the following error message: "Page cannot be opened because Safari could not connect to the server".

This has a technical background. For a traditional desktop system (Windows or Mac), the link to call the AusweisApp2 is
http: //127.0.0.1:24727/eID-Client..., but on mobile systems it is eid: //127.0.0.1:24727/eID client.... iOS devices can only process one call of the AusweisApp2 in the form "eid://". However, since Safari acts as a desktop browser in the above case, the AusweisApp2 is incorrectly called via a "http://" link.  

As a workaround, you can manually change the "http://" to "eid://" in the Safari address bar at http:// 127.0.0.1:24727/eID-Client... and reload the page to continue the badge process in the AusweisApp2.

You can also permanently deactivate the Dekstop browser call in the iPad settings. To do this, call up the "Settings" app on your iPad, then "Safari". In the section "Settings for Websites" (scroll down a bit) you can manually deactivate the button "Request desktop website on".

Which screen readers can be used?

AusweisApp2 for the operating system Windows supports the screen reader "JAWS." AusweisApp2 for the operating system Mac OS X / MacOS / iOS supports the built-in screen reader "VoiceOver".

What are Transport PIN, CAN and PUK?

Transport PIN
You have received a 5-digit transport PIN by mail, which you must change to a new 6-digit PIN under "PIN management" before using the online ID function. This is how setting the PIN works.

CAN
The card access number (CAN) is only required if you have entered the wrong PIN twice already. In order to prevent that a wrong PIN is entered for a third time without your consent, thus blocking your card, you have to enter the CAN at this point. The CAN is a 6-digit number that you can find on the front side of your ID card at the bottom right.

PUK
After entering the PIN incorrectly three times, the PIN will be blocked. You can unblock it using the PUK you received with your PIN letter. However, the PUK can only be used up to ten times. After entering the PUK, you must enter the correct PIN again.

PIN forgotten or transport PIN incorrect - what to do?

PIN forgotten
You can set a new PIN free of charge at your local citizens' registration office. Unfortunately, this is not possible directly in Ausweisapp2 because of security reasons.

Transport PIN wrong
Please contact the authority which issued your ID card. They can check whether your online ID card is working properly or whether the transport PIN was transmitted incorrectly. You can find out about the opening hours, contact persons and responsibilities of offices and authorities in your area by calling the public authorities hotline 115 or on the Internet: http://www.behoerdenfinder.de.

How do I change my transport PIN / Error "Time exceeded"?

After applying for your ID card, you will receive a letter containing information about the online identification function. This contains, among other things, the so-called transport PIN. The transport PIN is a 5-digit number that you must replace with a 6-digit PIN of your own choice before using the online ID card function for the first time. You can do this either at your local citizens' registration office when you pick up your ID card or later in AusweisApp2.

And this is how it works: 

  1. In AusweisApp2, select the menu item "Change my (Transport) PIN" and then select "Five-digit Transport PIN".
  2. If you are using AusweisApp2 directly on your smartphone, place your ID card on the NFC interface of your smartphone. If you are using AusweisApp2 on a PC or laptop, you must connect a smartphone as a card reader or an USB card reader before changing the PIN.
  3. Enter the transport PIN from your PIN letter above. 
  4. Now enter your new 6-digit PIN. Choose a number combination that is not easy to guess, i.e. neither "123456", nor your date of birth or other combinations printed on the ID card. 
  5. Confirm the new PIN by entering it again.

If you are to use AusweisApp2 on a PC or laptop and have connected a card reader with a display, enter the transport PIN and then your new PIN twice without being explicitly prompted (enter transport PIN -> OK, enter new PIN -> OK, enter new PIN-> OK).

Please note that the time in which the PIN change must be completed is only one minute. If you exceed this time limit, the error message "Time exceeded" will be displayed. In this case, restart the process.

What is the online identification function?

The online identification function of your national identity card, electronic residence permit or eID card allows you to prove your identity securely and without any doubt on the Internet, at Bürgerterminals (self-service terminals at your citizen centre) and other terminals. This function also allows you to determine the identity of any party you are dealing with on the Internet. Further information about the online identification function is available on the website of the Federal Ministry of the Interior, Building and Community: www.personalausweisportal.de.

Where can I use the online identification function?

You can make use of various services that use the online identification function, for example authorities, insurance companies or banks. You can find an overview of available services in our provider list.

At this point, we would like to expressly point out that the AusweisApp2 is only responsible for the software for using the online identification function and not for the services offered. If you have any questions regarding a specific service, please contact the provider directly.

How to use a smartphone or tablet for direct readout via NFC

Reading the online ID chip and securely transferring your data can be done directly via NFC on many mobile devices. To do this, your smartphone and your online ID card must be placed on top of each other at the respective NFC interface and the data transfer must be confirmed by entering your PIN. In addition to the basic requirement "NFC supported", three further functionalities are required for this:

  1. An Android smartphone or tablet with Android version 5.0 and up or an iPhone with iOS 13.1 or up.
  2. The firmware/operating system of the device must support Extended Length communication. Extended Length enables the transmission of data packets longer than 261 bytes to and from the online ID card or the encryption of the data.
  3. For a stable connection during data transmission, the NFC chip installed in the smartphone must have a correspondingly sufficient field strength.

Which card readers are supported by AusweisApp2?

An overview of compatible card readers with AusweisApp2 can be found here. Basically, all external card readers certified by the German Federal Office for Information Security (BSI) are supported and tested in connection with AusweisApp2. 

In addition to USB card readers, you can also use suitable, NFC-enabled smartphones to read the online ID card. You can use AusweisApp2 directly on your smartphone or connect the smartphone as a card reader with other devices. You can find further information about suitable smartphones here.

Which mobile devices can be used for the Online Identification Function via NFC?

Not every smartphone or tablet can be used for reading the online ID card. The mobile device must support the following requirements around the NFC technology:

  1. Android version from 5.0 upwards/ iOS version from 13.1 with an iPhone 7 upwards.
  2. The device must support the NFC function. For a stable connection during data transmission, the built-in NFC chip must have a correspondingly sufficient field strength here.
  3. The firmware/operating system of the device must support extended length communication. Extended Length enables the transmission of data packets with a length of more than 261 bytes from and to the online ID card or the encryption of the data.

An overview of suitable mobile devices can be found here.

How to use a NFC-enabled device as a card reader (with another mobile device or a PC)

Using the function "Smartphone as card reader", you can pair a suitable smartphone with a PC/ laptop (Windows or Mac), an iPad or a non-NFC-capable Android device.

Requirements for suitable smartphones:

  1. A smartphone or tablet with Android version 5.0 and up or an iPhone 7 version 13.1 or higher.
  2. The smartphone must support the NFC function. For a stable connection during data transmission, the NFC chip built into the smartphone must have a correspondingly sufficient field strength.
  3. The firmware/operating system of the device must support extended length communication. Extended Length enables the transmission of data packets with a length of more than 261 bytes from and to the online ID card or the encryption of the data.

How it works:

  1. Connect both devices to the same WLAN. (Note: You must allow all devices on your network to communicate with each other, including your smartphone. You can usually adjust this in the router or network settings.)
  2. If necessary, turn on NFC on the smartphone that will be connected as a card reader.
  3. Start remote access in AusweisApp2 on the smartphone that is to be connected as a card reader.
  4. Start pairing and connect devices by entering the pairing code.

Detailed instructions for pairing the AusweisApp2 with a smartphone can be found here.

Is identification on mobile devices as secure as with a card reader?

In terms of security, using a smartphone as a card reader is comparable to using a basic card reader on a computer (security class 1). This is because the device on which the PIN is entered is always critical to security. Malware which could read the PIN, especially keyloggers, could be present here under certain circumstances. We therefore recommend using up-to-date operating systems and virus scanners to prevent this. Compared to basic card readers and smartphones, the PIN never reaches the computer when using a convenience reader and can therefore not be intercepted (security level 3).

However, with the PIN alone, no one can misuse your online ID card. The principle of possession (online ID card) and knowledge (PIN) always applies. If you do not have both components, you cannot use the online ID function.

What is NFC?

NFC stands for Near Field Communication and is an international transmission standard based on RFID technology for the contactless exchange of data. RFID in turn stands for Radio-Frequency Identification. This technology enables identification via electromagnetic waves. Radio waves enable mobile devices such as smartphones or tablets to identify and locate each other automatically and without contact. RFID technology operates in accordance with ISO/IEC 14443 / -4 and is designed for a range of 5 to 10 cm.

Why do you need NFC for (mobile) use of the AusweisApp2?

A contactless RFID chip is integrated in your online ID card. This means that the online ID card can be read via electromagnetic waves - after you have enabled transmission by entering your PIN. The counterpart is an external card reader or a smartphone that can be used as a card reader. The card reader or smartphone must support NFC in accordance with the ISO standard IEC 14443 / -4. The necessary power supply for the online ID card is realized via induction.

Why does the online ID function not work even though contactless payment via NFC (Google Pay, Apple Pay etc.) works perfectly?

Not every readout process via NFC is the same. The application of the online ID function cannot be technically compared with contactless payment. When paying, the payment terminal with its strong NFC antenna only reads a small amount of data from the phone's NFC chip in one direction.

With the online ID function, on the other hand, NFC communication takes place in both directions over a longer period of time. The amount of data transmitted here is larger and is encrypted. The power supply to the ID card is provided solely by the smartphone's NFC antenna. Therefore, there is a possibility that the power of the NFC chip installed in the smartphone does not have sufficient strength.

To improve the connection, a permanent and careful positioning of the ID is important. Depending on the mobile device, a too low battery level can also cause problems.

What is the challenge with extended length communication?

It is necessary that both the NFC chip and the operating system used on the smartphone support extended length communication. Only then can data and certificates be transmitted successfully. The current generation of commercially available NFC chips in Europe already supports Extended Length by default. However, the version of the Android operating system used is often a stumbling block. 

There is a field variable that is read by AusweisApp2 to check whether a smartphone supports Extended Length or not. This variable contains the information how big the packet length is, which can be transmitted during a readout process. For all Android versions up to 8.0, this variable indicates that only 261 bytes can be transferred. For the readout process to work, however, the device must report back that it can transmit a packet length of at least 500 bytes. This packet length is required by AusweisApp2 or the online ID card mainly to implement the security protocols, such as PACE (encryption).

With the Android 9 operating system, Extended Length is enabled by default (cf. issuetracker.google.com/issues/37005118). In detail, this change means that smartphone manufacturers can/must now configure how many bytes can be transferred at once when using an Android operating system.

What is the challenge with the field strength of the NFC chip?

Practice has shown that many manufacturers reduce the field strength of the NFC chip to positively influence the battery life. Unfortunately, this leads to communication with the online ID card becoming unstable or not working at all. The reason for this is that in this case the RFID chip in the online ID is not supplied with sufficient energy. The exact specifications for field strength can be found under point 6.2 in ISO standard 14443-2. (Tags that use ISO 14443 for communication are part of Class 4, which results in a minimum field strength of 2.0 A/m and a maximum field strength of 12 A/m).

I encounter problems with my external card reader/ My card reader is not recognized

The non-recognition of your external card reader may be related to an outdated device driver. Please check the up-to-dateness of the device driver you are using and install a more recent version if necessary. You may need to reboot your system afterwards.

General notice:
As the manufacturer of the software AusweisApp2, we have no influence on the software up-to-dateness of third-party providers.

Notes on the card reader HID Omnikey 5321:
When using the card reader "HID Omnikey 5321", the ID card must be removed from the card reader after an authentication or PIN change, otherwise error messages may occur. Please wait a few seconds before replacing the badge.

My smartphone does not recognize the online ID card

Your mobile device does not recognize the online ID card or reports "ID card removed"? (Direct readout)

There can be several reasons for this:
a) The ID card has been moved and lost contact with the NFC interface.
b) The position of the ID card is not optimal or the field strength on the NFC chip is too low. In the course of the identification process, the identity card will then not get enough energy.
c) Some mobile devices deactivate the NFC interface after prolonged contact with the card for power-saving reasons, as known to Samsung, for example. Unfortunately, the AusweisApp2 can not influence this behavior. An NFC connection can then only be re-established after either the screen has been switched off and on again or NFC deactivated and activated again.

You are using your smartphone as a card reader and the device does not recognize the ID card?

To successfully pair your smartphone as a card reader, please refer to the FAQ article "How to use a NFC-enabled device as a card reader". Also consult the list of suitable smartphones available on the website under the menu item "Compatible devices".

How do I achieve a stable connection between ID card and smartphone?

First of all, it is important that you place the online ID card directly on the NFC interface and make sure tthat a stable position is maintained. Please note here that mobile devices often do not have the NFC chip installed in the center. You should therefore try out different positions. If we know the position of the NFC interface, you can find it in our list of suitable smartphones. In addition, make sure that your mobile device is in contact with your online ID card at all times. During use (PIN entry, readout process), the NFC connection must not be interrupted. Protective covers or NFC-enabled cards (e.g., credit cards) stored in them can additionally restrict connectivity.

What does "scan ID" mean in the iOS version of AusweisApp2?

Apple uses the term "scanning" to describe the process of reading via NFC. "Scan ID card" describes the process in which AusweisApp2 communicates with the ID card to check whether the online ID function is activated and to read out the data after it has been authorized by entering the PIN. To do this, the ID card must be held directly against the iPhone for some time, thus establishing a connection via NFC.

Why does the "Scan ID Card" process keeps failing with the iOS version?

During online identification, AusweisApp2 "scans" the card a total of two times (see also FAQ entry "What does "scan ID" mean in the iOS version of AusweisApp2?"). During the first scan, AusweisApp2 checks the status of the ID card via NFC, e.g. whether the online ID function is activated. This already works at a greater distance and a short connection time between iPhone and ID is sufficient. During the second scan, the actual reading process of the data from the ID chip takes place via the eID server. This process requires a somewhat longer, stable connection because a larger amount of data is transmitted, which is encrypted in the ID card for security reasons. The second scan therefore requires that the ID card may be placed more precisely or closer to the iPhone and that both - iPhone and ID card - must be held still for a while.

Why can't the NFC interface in the iPhone SE and 6S (Plus) be used for the AusweisApp2?

For reading out NFC cards, the so-called Core NFC Framework from iOS is used on the software side. For hardware reasons, Apple does not provide this for the devices mentioned above. Although payment terminals and some simple NFC tags are supported, communication with smart cards such as ID cards is not possible.

Why can't I connect a normal card reader to a mobile device via micro USB?

When implementing the mobile AusweisApp2, we focused on the use of the smartphone's NFC interface. Because, due to the generally rather low distribution and acceptance of external card readers, AusweisApp2 addresses card readers via the so-called smartcard specification/ library "PC/SC". This library is available, for example, for the Windows and Mac operating systems, but for mobile operating systems such as Android and iOS, PC/SC is not available by default or is severely restricted. 

By the way: Users are able to add more features to AusweisApp2. That is possible because the app is open source available at GitHub and can be customized according to one's own wishes and for the benefit of the entire community.

Why does my Android mobile device report "No supported app for this NFC tag" or "Perform action with..." when putting ID and Smartphobe together, but AusweisApp2 is missing in the displayed list of applications?

This or a similar message is displayed on Android devices by the NFC background service when the ID card (or another NFC-enabled card) is placed on the smartphone while AusweisApp2 is not in the foreground. Reading the ID card with compatible devices after a manual start of AusweisApp2 or in the course of an online authentication works independently of this. To avoid this message, do not place the ID on the mobile device until AusweisApp2 prompts you to do so.

Why does AusweisApp2 ask me to put on my ID card although no card reader is connected yet?

If you are asked to put on your ID card although you have not yet connected a card reader (USB-based or using a smartphone as a card reader), this could be because you are using a laptop with a built-in card reader. It is possible, however, that this is not able to read your ID card. If the integrated card reader does not work, we recommend using your smartphone as a card reader or a separate USB card reader. A list of suitable USB card readers can be found here.

Which providers are available?

At https://www.ausweisapp.bund.de/en/online-identification-function/provider-list/ and in the Providers section of AusweisApp2, you will find an overview of many providers of the online ID function.

Note: The list does not claim to be complete.

Why can't I find every provider in the provider overview?

Unfortunately, we are not informed about every available service. If you are a service provider yourself or know of a service that uses AusweisApp2 but is not listed in our provider list, please feel free to let us know. Simply send us a short, informal email with the name of the service and a link to support@ausweisapp.de - thank you!

Why aren't all providers available via smartphone?

This has a technical background. A provider's website starts AusweisApp2 via a specific link. For desktop systems (Windows & Mac) the link is "http: //127.0.0.1:24727/eID-Client", on mobile systems "eid: //127.0.0.1:24727/eID-Client".

If this so-called mobile call is not implemented correctly by the provider, you will receive the error message "127.0.0.1 / No connection to server..." on your smartphone. In this case, please inform the provider directly about the issue.

As a workaround, you can manually change the "http://" to "eid://" in the address bar of your browser at "http://127.0.0.1:24727/eID-Client" and reload the page in order to continue the identification process in AusweisApp2.

We have already notified the providers we know of about the issue, but unfortunately we have no influence on the timing of the mobile link implementation.

Why do I get an error message in the browser from the service provider on Windows/ macOS?

If you have not started AusweisApp2 before using a service on your PC or laptop, you will receive error messages such as "The website cannot be reached" or "Connection failed". To fix the problem, please start AusweisApp2 and open the respective service again.

Why do I get an error message after a successful identification process when I am redirected from AusweisApp2 to the service provider?

Possible reason: Default browser

After a successful identification process, it may happen that your browser displays an error message (e.g. "Page not found" or "Error") when forwarding from AusweisApp2 to the service provider. To avoid such an error, please use the browser that you have set up as the default browser in your system for the entire process.

Possible reason: Incognito mode in the browser

The same error message (e.g. "Page not found" or "Error") also occurs when you access a service provider's website using the incognito mode. When the user is redirected back to the browser after a successful identification process, the service provider may no longer be able to assign the session due to the way incognito mode works, since the security-relevant cookies are no longer present.

To troubleshoot, simply visit your service provider's website directly in the default browser at the start of the process and do not use incognito mode. On Android devices and devices with iOS 14.0 and higher, you can set the default browser yourself; Safari/Chrome or the manufacturer's browser are usually preset. On iOS 13, the default browser is fixed to Safari by the manufacturer.