The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different principal than the inbound token. The information in the logon accelerator token was ignored in favor of the information in the inbound token. Depending on the audit policy, further details of this token may be written to a 10530 event with the same transaction ID.
The client presented a certificate that could not be mapped to an Active Directory Domain Services user account. Error code: ...
The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
The client presented a valid inbound token as evidence. Token ID: %4 Issuer: %5 Audience: %6 Effective time: %7 %8 Expiration ...
The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...