<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
0D54z00009qWXRUCA4Okta Classic EngineMulti-Factor AuthenticationAnswered2025-10-11T09:00:47.000Z2023-11-23T08:03:45.000Z2023-11-26T17:27:37.000Z
  • b5n6c (b5n6c)

    Hi Enrico,

    Thanks for contacting the OKTA Community.

    Prerequisites for this use case is that first you have to integrate the custom authenticator. Please refer this docx :- Custom authenticator integration guide | Okta Developer

    Go to okta admin console > go to security > Click on authenticators > Click on Add authenticator > Click add custom authenticator

     

    Interface will open, where you'll have to add the details of the custom authenticator and assigned to particular application.

    For detailed view of the fields please refer this docx :- https://help.okta.com/oie/en-us/content/topics/identity-engine/authenticators/custom-authenticator.htm

     

    After adding custom authenticator you have to set-up in the enrollment Policy.

    Expand Post
    Selected as Best
  • EnricoR.01614 (Customer)

    Still not clear to me how the custom authenticator could communicate to TACACS server. Which option to choose in the application creation and if there is the need to add some code to manage the notifications. Is there any documentation or examples showing such integration with more details ? Documentation for smilar integration with RADIS server could help too. Thanks.

This question is closed.
Loading
SAML v2 IDP and TACACS in MFA