locked
User unable to login Relying Party Trust providers externally RRS feed

  • Question

  • Hello,

    We have a ADFS Server Farm, 2 Windows server 2019 ADFS internal, 2 Windows Server 2019 Proxy servers in DMZ. Everything works fine.

    We have a problem with one of our users (only one of almost 2000). The user can login to all applications using Federation with ADFS from the internal network. But can't login to any of these applications from external networks. The applications that are used with ADFS are Office365, Afas, Topdesk, etc.

    When we login with the user account we are redirected to the ADFS page, we type in the password the screen is refreshed and we need to type in the username and password. It looks like a login loop. Other users do not have this problem.

    In the eventlog we see the following messages:

    A logon was attempted using explicit credentials.

    Subject:
    Security ID: <Domain>\sysADFS
    Account Name: sysADFS
    Account Domain: <Domain>
    Logon ID: 0x8EFD6
    Logon GUID: {5a162718-6af3-c700-f69f-48558d54e27a}

    Account Whose Credentials Were Used:
    Account Name: User1
    Account Domain: <Domain>
    Logon GUID: {0cbac4f5-0db3-2328-ff6f-d9ab876cb61f}

    Target Server:
    Target Server Name: localhost
    Additional Information: localhost

    Process Information:
    Process ID: 0xf7c
    Process Name: C:\Windows\ADFS\Microsoft.IdentityServer.ServiceHost.exe

    Network Information:
    Network Address: -
    Port: -

    This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials.  This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.

    -------------------------------------------------------------------------------------------------------------------------------------------

    An account was successfully logged on.

    Subject:
    Security ID: <Domain>\sysADFS
    Account Name: sysADFS
    Account Domain: <Domain>
    Logon ID: 0x8EFD6

    Logon Information:
    Logon Type: 3
    Restricted Admin Mode: -
    Virtual Account: No
    Elevated Token: No

    Impersonation Level: Impersonation

    New Logon:
    Security ID: <Domain>\User1
    Account Name: User1
    Account Domain: <Domain>
    Logon ID: 0x7B40A5B0
    Linked Logon ID: 0x0
    Network Account Name: -
    Network Account Domain: -
    Logon GUID: {0cbac4f5-0db3-2328-ff6f-d9ab876cb61f}

    Process Information:
    Process ID: 0xf7c
    Process Name: C:\Windows\ADFS\Microsoft.IdentityServer.ServiceHost.exe

    Network Information:
    Workstation Name: ADFS06
    Source Network Address: -
    Source Port: -

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

    This event is generated when a logon session is created. It is generated on the computer that was accessed.

    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 occurred. The most common types are 2 (interactive) and 3 (network).

    The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

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

    The impersonation level field indicates the extent to which a process in the logon session can impersonate.

    The authentication information fields provide detailed information about this specific logon request.
    - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
    - 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.

    --------------------------------------------------------------------------------------------------------------------------------------------

    An account failed to log on.

    Subject:
    Security ID: <Domain>\sysADFS
    Account Name: sysADFS
    Account Domain: <Domain>
    Logon ID: 0x8EFD6

    Logon Type: 3

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

    Failure Information:
    Failure Reason: Account currently disabled.
    Status: 0xC000006E
    Sub Status: 0xC0000072

    Process Information:
    Caller Process ID: 0xf7c
    Caller Process Name: C:\Windows\ADFS\Microsoft.IdentityServer.ServiceHost.exe

    Network Information:
    Workstation Name: ADFS06
    Source Network Address: -
    Source Port: -

    Detailed Authentication Information:
    Logon Process: W
    Authentication Package: Negotiate
    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.

    ---------------------------------------------------------------------------------------------------------------------------------------------

    The user account is not Disabled, is nog Locked Out.

    Can login on Office365, Afas and other applications from internal network.

    Tried a password reset, doesn't work.

    If we login with the ADFS test URL: https://adfs.<domain>.nl/adfs/ls/idpinitiatedsignon.htm we get the same problem.

    If we give in the wrong password we get an error message that the username or password is incorrect.

    I hope anyone had a solution to our problem.

    Kind Regards



    • Edited by Seraphinus1990 Tuesday, January 7, 2020 2:21 PM Additional information.
    Tuesday, January 7, 2020 2:16 PM