<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
0D54z0000AE5OhQCQVOkta Classic EngineMulti-Factor AuthenticationAnswered2025-09-17T09:00:30.000Z2024-08-12T14:06:30.000Z2024-08-16T18:40:21.000Z

qhx3c (qhx3c) asked a question.

Radius Status Getting Failed. (Not able to Verify Radius Agent)

We need to have AWS Workspace MFA with OKTA. So to test this I have done following things.

Created an EC2 instance and installed OKTA radius agent.

Created AWS directory AWS Managed Microsoft AD.

IN MFA of created directory trying to enable MFA with radius agent but radius status getting failed.

Don't know what is the exact issue. Kindly help me to resolve this issue.


  • Mihai N. (Okta, Inc.)

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

     

    Unfortunately, there are too many variables to give an on point answer for the issue and the Okta Community Questions forum isn't really meant for in-depth troubleshooting, but I would recommend starting by reviewing this documentation on how to configure things on the Okta side and perhaps check this troubleshooting article that might provide additional insight.  

     

    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
  • qhx3c (qhx3c)

    @Mihai N. (Okta, Inc.)​ Thank you for answering.

    The document specifies choosing AD Connector as the Directory type, but I opted for AWS Managed Microsoft AD.

    So, I'm wondering if it won't work with AWS Managed Microsoft AD and if it's necessary to use AD Connector.

    • Mihai N. (Okta, Inc.)

      Hi @qhx3c (qhx3c)​ - it could be. I'm not familiar with the specifics of the configuration but as far as I can see on the AWS side docs and in conjunction with the configuration steps mentioned in our docs, those options are two different things.

       

      AWS Directory Service for Microsoft Active Directory is a feature-rich managed Microsoft Active Directory hosted on the AWS cloud. AWS Managed Microsoft AD is your best choice if you have more than 5,000 users and need a trust relationship set up between an AWS hosted directory and your on-premises directories.

      AD Connector simply connects your existing on-premises Active Directory to AWS. AD Connector is your best choice when you want to use your existing on-premises directory with AWS services. 

       

       

      Regards.

      --

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

      Expand Post
This question is closed.
Loading
Radius Status Getting Failed. (Not able to Verify Radius Agent)