Can I integrate the AusweisApp into my own App?
Yes, with the AusweisApp SDK, you can integrate the online ID function directly into your app. This means that there is no need to call up the AusweisApp separately. Identification runs seamlessly within your application.
What is the difference between the AusweisApp SDK on mobile devices and stationary systems?
The AusweisApp SDK on mobile systems is integrated into your application and installed together with it on the user's device (fully integrated). More information on control can be found here. In contrast, a partially integrated approach is used on stationary systems (Windows and macOS), where the AusweisApp is installed separately on the user's system (by the user themselves or by your application's installer). The SDK is controlled via the AusweisApp's WebSocket interface.
Where can I find the source code for the AusweisApp?
The AusweisApp is open source. The complete source code can be found on GitHub: https://github.com/Governikus/AusweisApp.
Is the AusweisApp SDK also available for native programming languages?
Yes, the SDK is also available for Swift (iOS) and Kotlin (Android) – as specially developed SDK wrappers for native app development. You can find them here.
How can I test whether my integration is working?
An official test infrastructure (‘test system’) is available to check your integration which simulates the eID infrastructure. To access it please contact your eID service provider, server manufacturer or identification service provider. Test ID cards and ID simulators are also available. More information can be found here.
Why do I get errors when trying to connect to the AusweisApp during testing?
In a test application, the TLS configuration (in particular, the interlocking of the TLS certificates with the authorisation certificate) may not have been carried out correctly. In the test environment you can activate the developer mode of the AusweisApp to diagnose these errors and bypass them for the test case. Information on developer mode can be found here.
How can I prevent users from being redirected to the wrong page after AusweisApp authentication?
The so-called ‘secure return’ must be implemented correctly. The return URL is checked by the AusweisApp to prevent phishing. Also ensure clean session management so that users return in the correct context. Pay particular attention to problems that can arise from ‘incognito’ or ‘private’ sessions and intercept them appropriately. Similar problems arise if the return is made to a different browser due to unsuitable default browser settings on the user's part.
My application is not receiving any data from the eID server – what could be the problem?
Ensure that communication between your back-end system and the eID server takes place via secure protocols (SOAP, SAML, OpenID Connect) with the recommended security configurations.
Note: Please contact your eID service provider.