Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 17 replies
  • Subscribers 4 subscribers
  • Views 18760 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to login to user portal with Active Directory user?

dswartz

So I set up an Active Directory backend group.  The test function authenticates just fine, but when I try to login with such a user in the user portal, it fails with 'Invalid username/password, or access denied by policy'.  I've tried to follow the HOWTO by balfson, but no luck.  Not sure where to proceed :(



This thread was automatically locked due to age.
  • 0 in reply to BAlfson

    I wonder if the portal is passing something I don't expect?  I am using the exact same name and password in the portal as in the authentication test, and the former fails, but the latter works.  And if the problem was on the AD end, I would expect to see an audit failure message (as I do in fact see if I enter a wrong password.)  Is there a way to turn up verbosity/debugging to see what the portal is doing?  Thanks!

  • 0 in reply to dswartz

    Just as another data point: I created an L2TP server on the sophos VM, specifying the same radius server with the same credentials.  It connects just fine, so it's something the portal is doing or not doing.

  • 0 in reply to dswartz

    Aha, success! (sort of).  I had been unable to get radius working from the portal either.  Perusing of the failure log on the DC, the portal is passing an authentication type of PAP, which is insecure, so disallowed by default.  As an experiment, I enabled the insecure protocols, and now, I can get to the User Portal.  I obviously don't want this as a 'real solution', so I think I have to have two NPS policies on the DC: one secure one for however authenticate for an SSL VPN, and one that allows PAP, but only from the portal.  Active Directory is still not working, but I think I have to declare victory and move on (although I'd love to know what the problem is...)

  • 0 in reply to dswartz

    A.D. integration works well.  You should open a support case.

  • 0 in reply to DouglasFoster

    A few more possibilities:

    • Based on other reports, rebooting UTM sometimes makes weird problems disappear.
    • Taking UTM out of AD (by rejoining it with an invalid login), deleting the object, and then rejoining AD will also fix some weirdness.   Do not remember if you have already done that.
    • Check whether there is a time synchronization problem.   UTM should connect to the PDC Emulator and get time from that machine as well.
  • 0 in reply to DouglasFoster

    Well, I'm stumped.  I hadn't joined the UTM to the domain with single sign-on - didn't think that was a requirement.  I have this in my two AD server configs:

     

    BIND DN: CN=Administrator,CN=users,DC=druber,DC=com

    BASE DN: CN=users,DC=druber,DC=com

     

    Test server settings and authenticate example user both work.  The portal doesn't.  When I click on limit users when defining the active directory group, it shows me as list of the normal users, which I can drag to the lower pane, and it looks okay.  My entry:

    CN=Dan Swartzendruber,CN=Users,DC=druber,DC=com

     

    In the above case, samAccountName is 'dswartz'.  This is what I tested authentication with for both AD servers, and it works.  Is this maybe not what should be going in the user portal username box?

  • 0 in reply to dswartz

    As far as I know, if you using an Active Directory authentication server, you are expected to configure the single sign-on tab so that UTM joins the domain.  I have never heard of anyone doing it otherwise, but it may be supported.   Another reason to ask support for help.

    You can use LDAP instead of Active Directory.  It is necessary if you need to support a second, third, or fourth Active Directory domain, since UTM can only join one domain.  In my experience, LDAP behaves interchangeably with AD.   If want to use LDAP, review my writeup in the Wiki section for a detailed tutorial.

    The key differences between the two is that an Active Directory PC creates a session using the computer account, then uses the computer account to validate the user login.   In LDAP mode, the program uses a user account to log in with administrative privileges, then uses that user account to validate the other user login.

Unfiltered HTML