locked
UAG and dot naming convention - authentication fails RRS feed

  • Question

  • HI all,

       We're currently evaluating UAG for use with our customer website, to start replacing our Novell iChain (and related) products.

       We're running into problems with authenticating our customer accounts - all of which are in user.name@company.com format.  The UAG logs show an error of "No such object".  For now the backend authentication source is Novell Directory.

     

       Running a packet capture on our eDir server, we discovered that the bind request from UAG for user.name@company.com ends up being "cn=user,ou=name@company,o=com" instead of "cn=user.name@company.com".  It is using the "dot" as a separator for the LDAP DN.

     

       Is there a way to change this behavior?  Any workarounds?

     

    Friday, October 28, 2011 9:05 PM