Unable to login to user portal with Active Directory user?

On the user portal configuration, you need to specify the groups that are allowed to use the portal.  Could this be the missing step?

Unfortunately, no.  I've tried with 'all users' checked and unchecked (in the latter case, I dragged the 'Backend Users' group to the DND pane...)  I *do* see various audit entries being made in the 2012 hosts's security log, but they are all 'success' entries.  It seems almost like whatever is being sent back by AD is being rejected by Sophos.  As an experiment to test that theory, I tried logging in as an AD user with a deliberately bad password and see this:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          1/22/2019 2:32:36 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      bdc.druber.com
Description:
An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:        BDC$
    Account Domain:        DRUBER
    Logon ID:        0x3E7

Logon Type:            3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:        dswartz
    Account Domain:        DRUBER

Failure Information:
    Failure Reason:        Unknown user name or bad password. <=============== this was the login attempt with bogus password!
    Status:            0xC000006D
    Sub Status:        0xC000006A

Process Information:
    Caller Process ID:    0x1cc
    Caller Process Name:    C:\Windows\System32\lsass.exe

Network Information:
    Workstation Name:    BDC
    Source Network Address:    10.0.0.74
    Source Port:        52820

Detailed Authentication Information:
    Logon Process:        Advapi  
    Authentication Package:    MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    Transited Services:    -
    Package Name (NTLM only):    -
    Key Length:        0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Oh, and 10.0.0.122 is my windows 10 workstation that I am trying to connect to the portal with...

I think also this is not specific to AD.  If I disable 'adirectory' and enable either of the radius servers, I get the exact same failure.  Same log snippet here:

2019:01:23-16:20:00 gateway aua[652]: id="3006" severity="info" sys="System" sub="auth" name="Server 10.0.0.13 (adirectory) is disabled"
2019:01:23-16:20:00 gateway aua[652]: id="3006" severity="info" sys="System" sub="auth" name="Server 10.0.0.7 (radius) is disabled"
2019:01:23-16:20:00 gateway aua[652]: id="3006" severity="info" sys="System" sub="auth" name="Trying 10.0.0.13 (radius)"
2019:01:23-16:20:00 gateway aua[652]: id="3005" severity="warn" sys="System" sub="auth" name="Authentication failed" srcip="10.0.0.122" host="" user="dswartz" caller="portal" reason="DENIED"

The UTM log is saying that your AD server has denied authentication.  Unless this is a new bug in V9.6, this has to be an issue with the DC and/or the password and/or the Backend Group and/or the Security Group in AD.

Cheers - Bob

That's what I thought, but then why does it print an audit failure in the AD log when i enter an explicitly wrong password?  Also, I just retried the authentication test in the 'adirectory' screen and it worked, and I see this:

2019:01:23-16:37:31 gateway aua[2236]: id="3006" severity="info" sys="System" sub="auth" name="Authentication test request: m:adirectory, f:none, u:dswartz, ip:0.0.0.0, host:"
2019:01:23-16:37:31 gateway aua[2236]: id="3006" severity="info" sys="System" sub="auth" name="Testing method adirectory"
2019:01:23-16:37:31 gateway aua[2236]: id="3006" severity="info" sys="System" sub="auth" name="Trying 10.0.0.13 (adirectory)"
2019:01:23-16:37:31 gateway aua[2236]: id="3006" severity="info" sys="System" sub="auth" name="Authentication test successfull"

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!

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.

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...)

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

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.

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?