Release Note - Push Authentication [mPass AS 4.5 - V 4.5]

Modified on Wed, 25 Sep at 9:39 AM

mPass Push Authentication Release Notes


This release contains Push Authentication feature in mPass:

 

1. Available for RADIUS, OWA, windows login, and any in-house applications authentications

2. New configuration in mPass administration portal to configure mPass Push service URL, Client key, Client Secret and push time-outs

 

Configurations & Testing:

Define mPass push authentication server in mPass:

1. Navigate to Home->Backend System->Backend System from the left menu

2. Click the system backend system for details

3. Click the BackEnd Parameters tab

4. Navigate to the mPass Push Authentication configuration panel

5. Select Service status as  Enabled and Enter Client Id, Client Secret, mPass Push Service Base URL and Push Authentication Time-out (Secs)

6.  Click Save

7. Navigate to the policies and select your requried policy & enable the Push authentication in the MFA Control tab.

8. Now from the Users Management module, Click List Users & select the  required user. 

9.  Navigate to the MFA Control tab and click Push Authentication option and cick Update.

 

 

Activate mPass Authenticator or your branded push enabled application from   mPass User portal:

1. Ensure User's device is connected to the internet

2. Navigate to the mPass User portal

3. Login with user domain credentials

4. Navigate to Tokens Management and click Token activation

5. Follow the wizard and scan the QR code

 

Testing:

1. Login to the push authentication enabled application

2. Complete first factor authentication/just enter user name (for SSO applications)

3. Select Send push notification

4. User receives the Push Notification on his device

5. User confirms the response in the notification 

 


 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article