Forum Discussion

Bryan_Vance_171's avatar
Bryan_Vance_171
Icon for Nimbostratus rankNimbostratus
Apr 30, 2015
Solved

Error after setting NTLM authentication in iAPP

I am using the f5.microsoft_exchange_2010_2013_cas.v1.5.0 iAPP template, primarily for Outlook anywhere with auto discover, and after setting up the option for NTLM I get the following error after clicking finished:

 

script did not successfully complete: (list element in quotes followed by "-account-name" instead of space while executing "string map $map_array($item) $access_form" (procedure "iapp_apm_config" line 68) invoked from within "iapp_apm_config apm_map" invoked from within "if { $new_apm } { set aaa_pool [subst $apm_aaa($new_aaa_pool)] set pre_proc_map " [expr { $is_exchange_2010 ? "ses..." line:2561)

 

Does anyone know how to resolve this error?

 

Thanks,

 

application delivery
BIG-IP Access Policy Manager (APM)
devops
iApps
LTM
security
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Apr 30, 2015

    Specifically, what is the name of the NTLM machine account object you are selecting in the iApp?

     

9 Replies

Sort By
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Apr 30, 2015

    Hi Bryan, can you tell me which version of BIG-IP you are running on, as well as which options you chose when deploying the iApp?

     

    thanks

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Apr 30, 2015

    Specifically, what is the name of the NTLM machine account object you are selecting in the iApp?

     

    • Bryan_Vance_171's avatar
      Bryan_Vance_171
      Icon for Nimbostratus rankNimbostratus
      Apr 30, 2015
      The object name is f5 machine account and the account name is f5pair
    • mikeshimkus_111's avatar
      mikeshimkus_111
      Historic F5 Account
      Apr 30, 2015
      Aha! Generally, BIG-IP won't let you create objects with spaces or special characters in the name, however the NTLM machine account seems to not have any name validation. I just tested and was able to create accounts with all kinds of forbidden characters in the name. Some of them work with the iApp, but most don't. For now, you should be able to work around this by using a machine account name with only alphanumeric characters and underscores. We will get the deployment guide updated with this information and file a bug against the behavior. Thanks for bringing it to our attention!