14.2.1.2.11. Legacy PUSH Token¶
- class edumfa.lib.tokens.legacypushtoken.LegacyPushTokenClass(db_token)[source]¶
The Legacy PUSH Token uses the Firebase service to send challenges to the user’s smartphone. The user confirms on the smartphone, signs the challenge and sends it back to eduMFA.
The enrollment occurs in two enrollment steps:
- Step 1:
The device is enrolled using a QR code, which encodes the following URI:
otpauth://pipush/PIPU0006EF85?url=https://youredumfaserver/enroll/this/token&ttl=120
- Step 2:
In the QR code is a URL, where the smartphone sends the remaining data for the enrollment:
POST /ttype/push HTTP/1.1 Host: https://youredumfaserver/ enrollment_credential=<hex nonce> serial=<token serial> fbtoken=<Firebase token> pubkey=<public key>
For more information see:
Create a new token object.
- Parameters:
db_token (Token) – A database token object
- Returns:
A TokenClass object
- class PUSH_ACTION[source]¶
- ALLOW_POLLING = 'push_allow_polling'¶
- FIREBASE_CONFIG = 'push_firebase_configuration'¶
- MOBILE_TEXT = 'push_text_on_mobile'¶
- MOBILE_TITLE = 'push_title_on_mobile'¶
- REGISTRATION_URL = 'push_registration_url'¶
- SSL_VERIFY = 'push_ssl_verify'¶
- TTL = 'push_ttl'¶
- WAIT = 'push_wait'¶