<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AFqvQRCQZOkta Classic EngineAuthenticationAnswered2025-09-29T09:00:35.000Z2024-09-22T10:38:13.000Z2024-09-30T16:31:04.000Z

q8ozk (q8ozk) asked a question.

RADIUS application failing - 'failed user.authentication.auth_via_radius'

Trying to set up Okta RADIUS application. I got the latest Okta RADIUS agent 2.22.0 installed. The network traffic is confirmed.

 

Using Okta Verify MFA.

 

Application set up with superuser account and set to look for SAM account name, which is what I use to test (from AWS Workspaces).

 

From the application's logs:

 

(The ClientAddress field below is the SAM account name being tested with.)

 

Thanks in advance for any helpful guidance.

 

Image is not available

Image is not available

 


  • Mihai N. (Okta, Inc.)

    Hi @q8ozk (q8ozk)​ , Thank you for reaching out to the Okta Community! 

     

    The most common causes for authentication issues with the RADIUS app are:

    • Port misconfiguration - when you set it up it defaults to 1812 - you mentioned that network traffic is fine, so it's probably not that 
    • Wrong Secret key - the secrete key from the app on the Okta side must match with the one on the client gateway - perhaps double-check that in case it was incorrectly copied. 
    • Wrong (application) username - in the app configuration on the Okta side, check that the "Application username format" matches the expected value. 

    When you initially set up the app it defaults to "Okta Username" which might not be the expected value. Looking at the setup docs, it mentions having to use Email, you mentioned using the SAM account name. If you do end up making changes to that, make sure you hit the "Update now" option after saving the changes so it applies the update to the previously assigned users.   

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
  • q8ozk (q8ozk)

    Yes, the SAM account name is correct; yes, I can log into Okta admin using those credentials and the MFA that's associated to it in Okta Verify.

  • Mihai N. (Okta, Inc.)

    Hi @q8ozk (q8ozk)​ , Thank you for reaching out to the Okta Community! 

     

    The most common causes for authentication issues with the RADIUS app are:

    • Port misconfiguration - when you set it up it defaults to 1812 - you mentioned that network traffic is fine, so it's probably not that 
    • Wrong Secret key - the secrete key from the app on the Okta side must match with the one on the client gateway - perhaps double-check that in case it was incorrectly copied. 
    • Wrong (application) username - in the app configuration on the Okta side, check that the "Application username format" matches the expected value. 

    When you initially set up the app it defaults to "Okta Username" which might not be the expected value. Looking at the setup docs, it mentions having to use Email, you mentioned using the SAM account name. If you do end up making changes to that, make sure you hit the "Update now" option after saving the changes so it applies the update to the previously assigned users.   

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
This question is closed.
Loading
RADIUS application failing - 'failed user.authentication.auth_via_radius'