Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

Radius timeout for proxy targets & Microsoft Azure MFA/NPS

This thread has been viewed 17 times
  • 1.  Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted Nov 26, 2018 02:05 PM
      |   view attached

    We are in the process of looking at using Clearpass to Proxy Radius requests to Microsoft NPS and then onto Azure for MFA authentication. I have gotten this to work however I ran into an issue.

     

    (Right now Microsoft NPS is the only way to talk to Microsoft Azure MFA)

     

    I noticed that in Clearpass under Server Configuration, the maximum response delay for Radius can only be set to a maximum of 5 seconds, however, Microsoft is recommending up to 60 second delay as the user will either have to enter a token code or approve of the request via the Authenticator app.

     

    Is there a workaround?

     

    This seems to have been an issue with TACACS at one point and seems to be addressed but not for Radius:

     

    https://community.arubanetworks.com/t5/Security/ClearPass-TACACS-timeout/td-p/433414

    https://www.arubanetworks.com/techdocs/ClearPass/CP_ReleaseNotes_6.7.3/Default.htm#WhatsNew/NewFeatures_PolicyMgr.htm

     

    For multi-factor authentication (MFA) workflows that use TACACS+, a new TACACS+ Authentication Timeout service parameter lets you specify the TACACS server’s timeout interval. The default value for this parameter is 30 seconds. The minimum allowed value is 1 second, and the maximum allowed value is 300 seconds (5 minutes). Previously, the default timeout value was 10 seconds and could not be changed. An extended TACACS+ timeout interval might be needed when MFA workflows such as phone calls or text messages are used, which can take longer for the user to complete. To use this feature, go to the Administration > Server Manager > Server Configuration and select the service. On the Service Parameters tab, select Tacacs server as the service and then configure a value for the TACACS+ Authentication Timeout parameter. (#43268)



  • 2.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    EMPLOYEE
    Posted Nov 26, 2018 02:07 PM
    You can use Azure MFA Server directly from ClearPass.


  • 3.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted Nov 26, 2018 02:19 PM

    Tim, from what I have read you can only connect to Azure MFA if you have an on-prem MFA server.  We are using the Azure cloud MFA server.  

     

    Are you sure you can connect to the cloud MFA?  If so, how?



  • 4.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted Nov 26, 2018 02:20 PM


  • 5.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    EMPLOYEE
    Posted Nov 26, 2018 02:21 PM
    Yes, Azure MFA server which is a standalone server. You do not need to proxy through NPS.


  • 6.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted Nov 26, 2018 02:25 PM

    Yes, I know about the standalone server however I've been told by our Windows group that we will not be deploying the onsite MFA server as it adds complications into our setup.

     

    So I have no choice but to proxy through a NPS server with the MFA plugin



  • 7.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted May 22, 2019 11:03 AM

    Hey TIm, any documentation on how to set up on prem Azure?

     

    I am working on an Azure MAF - Cisco ASA  - Clearpass integration for VPN users.

     

    Thanks,



  • 8.  RE: Radius timeout for proxy targets & Microsoft Azure MFA/NPS

    Posted Feb 28, 2019 05:27 AM

    Hi,

    sorry to "misuse" this thread.

    We do also run MS Azure MFA in the same config you do but we ran into an issue:

    The MS NPS Server is only "talking" EASCII but NOT utf-8, this leads to several characters not beeing correctly interpreted. 

    I have not found a way to either use utf-8 on the MS NPS nor EASCII on the ClearPass.

     

    Did you run into the same issue or do you have any workaround?

     

    Thanks for taking the time to read this