Forum Discussion

paul_125686's avatar
paul_125686
Icon for Nimbostratus rankNimbostratus
Dec 16, 2013
Solved

Health Monitor with NTLM authentication - iApp generated vs Custom built

I have been working on creating a Health Monitor for SharePoint which uses NTLM authentication. I basically mirrored an existing HTTPS Health Monitor that the Exchange 2010 iApp generated and then ad...
application monitors
BIG-IP Access Policy Manager (APM)
deployment
devops
iApps
ntlm
security
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Dec 16, 2013

    Hi Paul, which version of BIG-IP are you running? The SharePoint iApp that ships with v11.4 includes an option to use NTLM for the health monitor. An RC version of this iApp is also avaialble for pre-11.4 BIG-IP.

     

    The OWA monitor is actually not logging on to OWA; rather, it's checking that it can access the logon.aspx page, which is set to anonymous access by default. That's probably why it doesn't matter when you change the CR/LF in the send string.

     

    Mike

     

paul_125686's avatar
paul_125686
Icon for Nimbostratus rankNimbostratus
Dec 16, 2013

Hi Mike,

 

Thanks for the response. We are running 11.3 HF5. I used the Sharepoint iApp that was on the system but it never asked for username or password as part of the template. I used a similar monitor (Exchange 2010 iApp generated) which I assumed was using the fields populated in the username field (domain\username)". Based on the cUrl test I see it doesn't need username at all for the monitor to get the expected response.

 

I guess the template just populated the fields even though it doesn't require them.

 

Thanks again.