What Is Push Notification Authentication?
Push Notification Authentication is a feature that lets you authenticate when logging in to TrustLogin by clicking a notification sent to your mobile device, instead of entering a password.
Note: A TrustLogin Pro Plan subscription is required to use this feature. For pricing, click here
▼ Watch the Push Notification Authentication introduction video here
How to Use It
The administrator assigns the option
↓
The member (user) registers the device that will approve Push Notification Authentication
↓
The member (user) registers their login browser at first login, and approves the login on each subsequent login
List of Push Notification Authentication Setup Guides
Please refer to the pages below for instructions on setting up Push Notification Authentication.
1. (For Administrators) Assigning Members and Sending Approval Device Registration Emails
2-1. (For Members) Registering an Approval Device [PC]
2-2. (For Members) Registering an Approval Device [Mobile]
3-1. (For Members) How to Log In (Initial Browser Registration and Subsequent Logins) [PC]
3-2. (For Members) How to Log In (Initial Browser Registration and Subsequent Logins) [Mobile]
4. (For Administrators) Removing a Member Assignment and Deleting an Approval Device
5. (For Members) Deleting an Approval Device
Frequently Asked Questions
Q 1) How many approval devices can I register?
A 1) You can register up to 3 devices.
Q 2) No number is displayed on the screen shown below.
A 2) If no approval device has been registered, no number will be sent. Please register an approval device.
Q 3) I deleted the TrustLogin app from my smartphone, but I can't register an approval device.
A 3) You can register up to 3 approval devices. Deleting the TrustLogin app does not delete the approval device registration, so please refer to the manual below to delete it first. After that, please try registering again.
4. (For Administrators) Removing a Member Assignment and Deleting an Approval Device
5. (For Members) Deleting an Approval Device
Q4) Can Push Notification Authentication be combined with multi-factor authentication or IP address restrictions?
A 4) Yes, it can.
The order in which all authentication checks are performed is as follows:
1. IP address restriction — if OK, proceed to the next step
2. Client authentication — if OK, proceed to the next step
3. Desktop SSO — if OK, proceed to the next step
4. Push Notification Authentication, password authentication, AD password authentication, external IdP password authentication — if OK, proceed to the next step
5. Cookie authentication — if OK, proceed to the next step
6. One-time password (OTP) — if OK, log in
This is the order used.
Q5) How can I prevent members from adding approval devices from their profile themselves (i.e., have the administrator control the adding and removing of members' approval devices)?
A 5) You can control this from the settings under "Admin Page > Settings > Push Notification Authentication." Please refer to the manual below for setup instructions.
1. (For Administrators) Assigning Members and Sending Approval Device Registration Emails > How to configure user control over device registration and deletion
Q6) If a member's Push Notification Authentication assignment is removed, what happens to their registered approval devices?
A6) Any information registered as an approval device will be deleted. If the assignment is made again, the approval device will need to be registered again.
Q7) Sometimes I need to select a number shown on the screen when logging in with Push Notification Authentication, and sometimes I don't. What's the difference?
A7) A number is displayed the first time you log in after Push Notification Authentication has been assigned. Once you select the correct number, cookie information is registered in your browser, and number selection is not required for subsequent logins. If you use a different browser on the same PC, you will need to select a number again the first time you log in with that browser.
This feature is designed to prevent you from accidentally approving unauthorized access by someone other than yourself.