Forum Discussion

Joshua_106551's avatar
Joshua_106551
Icon for Nimbostratus rankNimbostratus
Feb 18, 2014

How to use NTLM to basically bypass the F5 APM login page?

Looking for a way to use NTLM to basically bypass the F5 APM login page?

 

The overall goal… ADFS can auto-authenticate users to Salesforce if they are on our LAN and a member of the domain via IWA/NTLM. With the implantation of APM users now have a portal even if they are local domain users.

 

Has anyone created an access policy to duplicate this process flow?

 

Thanks!

 

7 Replies

  • What kj07208 described above would work with Kerberos End-User auth, as the HTTP 401 Response can only be used in conjunction with Basic or Kerberos Auth scenario. If Kerberos auth is sufficient for you, you can try the setup based on this documentation here

     

    If you want to use NTLM, you can follow the description of how to set it up here

     

    Your setup would differ from the documentation as you don't need to setup Kerberos SSO on the backend for your use case - simply extracting username from the NTLM Auth should be sufficient and then you can use it in the SAML assertion to send to SalesForce.com, etc.

     

  • Thanks guys! I am going to test this out and will update. My desire is to just use NTLM, so I am going to run with that option first.

     

    • ndaems_145583's avatar
      ndaems_145583
      Icon for Nimbostratus rankNimbostratus
      Hi Joshua, We are trying to do the same... Were you able to implement the NTLM AUth to bypass the APM Portal? Thanks
  • I just did a write up on this here:

     

    https://devcentral.f5.com/articles/leveraging-big-ip-apm-for-seamless-client-ntlm-authentication

     

  • Michael, We have implemented the solution you provided. The problem we keep running into is the NTLM username variable is always blank. I have added several message box's throughout the flow and everything passes except the very last step which is the AD Query. I have tested via several browsers and firefox seems to work the best for us. One time we made some changes to browser settings and for one session we were able to see the username variable was set. Out of hundreds of tests only one time have we seen the username variable get populated.

     

    Thoughts?

     

    • Michael_Koyfma1's avatar
      Michael_Koyfma1
      Icon for Cirrus rankCirrus
      Something is really weird there. What version of the BIG-IP are you using? If things fail at AD Query, you need to concentrate your efforts on why. After successfully NTLM authentication and session in progress you should be able to look at the Session Variables in the reports and see the *.ntlm* values - if the username is populated there, then you need to focus on why AD Query fails. If not, perhaps you can post a copy of your access policy so that we can take a look?