The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither user principal name (UPN), e-mail, nor security ID (SID) claims. Token ID: %4 Issuer: %5 Common name: %6 User Action Ensure that this application is configured as a Windows NT token-based application instead of a claims-aware application in the Federation Service trust policy.
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 ...
The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither user ...
The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
The client presented a valid XML token, but an error occurred when generating a Windows NT token from the Active Direcotry ...