F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Christian_Nishi's avatar
Christian_Nishi
Icon for Nimbostratus rankNimbostratus
Aug 09, 2019

HTTP 401 Response - Missing Split domain from full username - V13.1.1.4

Hi there F5 community,   I'm struggling with an authentication error. Currently I'm using a logon page with the option "Split domain from full username" and it's working, for another scenario, I ...
application delivery
BIG-IP Access Policy Manager (APM)
boneyard's avatar
boneyard
Icon for MVP rankMVP
Aug 13, 2019
session.logon.last.username
  • Christian_Nishi's avatar
    Christian_Nishi
    Icon for Nimbostratus rankNimbostratus
    Sep 02, 2019

    I tried with several combinations, but still no luck

    session.logon.last.username and session.logon.last.logonname are using the right user (Domain\User)

    Looking on the APM log, I see:

     

    Username 'mydomain\myuser'

    AD module: authentication with 'mydomain\\myuser@trusteddomain'  failed: Client 'mydomain\\myuser\@trustedomain@trusteddomain' not found in Kerberos database, principal name: mydomain\myuser@trustedomain. Please verify Active Directory and DNS configuration. (-1765328378)

     

    I have a multidomain environment, AD auth is configured with Trusted Domains and looks like is using the default domain to complete the user name. Can't find a way to use the last.logonname or last.username agains the AD Auth...