Push Token

The push token uses the privacyIDEA Authenticator app. You can get it from Google Play Store or Apple App Store.

The token type push sends a cryptographic challenge via the Google Firebase service to the smartphone of the user. This push notification is displayed on the smartphone of the user with a text that tells the user that he or somebody else requests to login to a service. The can simply accept this request. The smartphone sends a cryptographically signed response to the privacyIDEA server and the login request gets marked as confirmed in the privacyIDEA server. The application checks for this mark and logs the user in automatically.

To allow privacyIDEA to send push notifications, a Firebase service needs to be configured. To do so see Firebase Provider. Configuration

The minimum necessary configuration is an enrollment policy push_firebase_configuration.

With the authentication policies push_text_on_mobile and push_title_on_mobile you can define the contents of the push notification. Enrollment

The enrollment of the push token happens in two steps. Step 1

The user scans a QR code. This QR code contains the basic information for the push token and a enrollment URL, to which the smartphone should respond in the enrollment process.

The smartphone stores this data and creates a new key pair. Step 2

The smartphone sends its Firebase ID, the public key of the keypair, the serial number and an enrollment credential back to the enrollment URL of the privacyIDEA server.

The server responds with it’s public key for this token. Authentication Triggering the challenge

The authentication request is triggered by an application just the same like for any challenge response tokens either with the PIN to the endpoint /validate/check or via the endpoint /validate/triggerchallenge.

privacyIDEA sends a cryptographic challenge with a signature to the Firebase service. The firebase service sends the notification to the smartphone, which can verify the signature using the public key from enrollment step 2. Accepting login

The user can now accept the login by tapping on the push notification. The smartphone sends the signed challenge back to the authentication URL of the privacyIDEA server. The privacyIDEA server verifies the response and marks this authentication request as successfully answered. Login to application

The application can check with the orignial transaction ID with the privacyIDEA server, if the challenge has been successfully answered and automatically login the user. More information

For a more detailed insight see the code documentation Push Token.

For an in depth view of the protocol see [the github issue](https://github.com/privacyidea/privacyidea/issues/1342) and [the wiki page](https://github.com/privacyidea/privacyidea/wiki/concept%3A-PushToken).