The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different principal than the supplied credentials. As a result, the token request failed. The client must first log off before supplying credentials for a different user. Depending on the audit policy, further details of this token may be written to a 530 event with the same transaction ID. Token ID: %15 Identity: %16
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 ...
The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...
The client presented a valid XML token, and a Windows NT token was created successfully. Token ID: %4 Issuer: %5 Identity: ...
The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither a ...