Troubleshooting: RADIUS Server Processing Error

Version Affected: RADIUS Server 2.x+
 
 

Overview

The RADIUS Server logs can show a UDPRadiusProcessor: Radius processing error entry, commonly during or after an upgrade. There are multiple potential causes, distinguished by the specific exception logged alongside that entry:

• See Cause 1 - The log shows java.lang.IllegalArgumentException: Decrypt value can't be empty
• See Cause 2 - The log shows java.lang.NullPointerException

These causes are not related, so a fix for one cause will not resolve the other.

 

In this article

• Cause 1: IdP Client Missing an API ID or API Key
• Cause 2: RADIUS Client Has a Blank Attribute Mapping

Cause 1: IdP Client Missing an API ID or API Key

The RADIUS Server log shows:

ERROR UDPRadiusProcessor: Radius processing error
java.lang.IllegalArgumentException: Decrypt value can't be empty

This occurs when one or more of the appliance's configured IdP Clients does not have its API ID or API Key filled in.

Resolution 1:

Do either of the following:

• Fill in the API ID and API Key for every listed IdP Client that is missing them.
• Remove any IdP Clients that are not in use and do not have an API ID or API Key filled in.

Cause 2: RADIUS Client Has a Blank Attribute Mapping

After upgrading RADIUS Server to a newer version, the log shows:

ERROR UDPRadiusProcessor: Radius processing error
java.lang.NullPointerException

During the upgrade, the newer version's code does not handle a RADIUS Client configuration that has a blank attribute mapping — the older version allowed this, but the newer version cannot process it.

Resolution 2:

1. Go to RADIUS Clients.
2. Check every client for any attribute that is mapped to a blank value.
3. Remove the blank mapping from that attribute and save.

If the upgrade has already failed, you may need to reinstall or revert the upgrade first, make these changes on the pre-upgrade version, and then upgrade again.


 

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.