Troubleshooting: RADIUS Shows "A Notification Is in Progress" When Logging In Again

Version Affected: All
 
 

Overview

When a user attempts to log in to a RADIUS realm again after a previous login attempt, RADIUS may respond with the message "A notification is in progress. You can accept it and enter N or request a new one by entering Y."

Cause

This happens when the user abandoned a previous login attempt after a Push Notification (Push-to-Accept, or P2A) had already been sent, without accepting or rejecting it. The RADIUS Agent's background process that checks the status of that earlier push is still running when the user starts a new login attempt, so RADIUS asks whether to keep waiting on the original push (N) or discard it and send a new one (Y).

Resolution:

If you do not want users to see this prompt at all, a setting in the RADIUS Agent's properties file can make it always discard the earlier push and send a new one automatically, without asking. This setting's boolean value works in reverse of what its name suggests, so follow the values below exactly rather than guessing:

1. On the RADIUS Agent server, navigate to C:\Program Files\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\conf.
2. Open the appliance.radius.properties file.
3. Add (or update) the following line:

offer_discard_current_push_authentication_request=true

4. Save the file.
5. Restart the RADIUS service.

By default, this property is false, which prompts the user to discard the earlier Push-to-Accept request before sending a new one -- this is the "A notification is in progress" message. Setting it to true skips that prompt and automatically discards the earlier push each time, sending a new one immediately.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.