PII is hidden in Event logs

Just trying to track down the source of an event log that keeps coming up.

System.ArgumentException: IDX12741: JWT: '[PII is hidden]' must have three segments (JWS) or five segments (JWE). at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken) in C:\agent2\_work\56\s\src\System.IdentityModel.Tokens.Jwt\JwtSecurityTokenHandler.cs:line 705 at Ice.Security.OpenIdConnect.TokenValidator.ValidateToken(String token, TokenValidationParameters validationParameters, ISecurityTokenValidator tokenValidator) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\OpenIdConnect\TokenValidator.cs:line 98 at Ice.Security.OpenIdConnect.TokenValidator.ValidateWithKeyRefresh(String token, TokenValidationParameters validationParameters, ISecurityTokenValidator tokenValidator, ITokenValidationFunctions originValidator) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\OpenIdConnect\TokenValidator.cs:line 79 at Ice.Security.OpenIdConnect.TokenValidator.Validate(String token, TokenValidationParameters validationParameters, ISecurityTokenValidator tokenValidator, ITokenValidationFunctions validationFunctions) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\OpenIdConnect\TokenValidator.cs:line 70 at Ice.Security.OpenIdConnect.TokenValidator.Validate(String token, String& alternateIdentityFieldToUse) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\OpenIdConnect\TokenValidator.cs:line 38 at Ice.Security.RestApi.AuthHelper.TokenAuthCheck(String headerValue) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\RestAuthHelper.cs:line 208 at Ice.Security.RestApi.AuthHelper.CheckAccess(String headerScheme, String headerValue) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\RestAuthHelper.cs:line 151 at Ice.Security.RestApi.AuthHelper.GetPrincipal(String headerScheme, String headerValue, IEnumerable`1 customHeaders, UserFileItem& userFile) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\RestAuthHelper.cs:line 121 at Ice.Security.RestApi.AuthHelper.CheckAccess(String headerScheme, String headerValue, IEnumerable`1 customHeaders) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.Ice\Security\RestAuthHelper.cs:line 71 at Epicor.RESTApi.Security.IceSecurityHelper.MakeAuth(IOwinRequest request) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.RESTApi\Epicor.RESTApi\Security\IceSecurityHelper.cs:line 41 at Epicor.RESTApi.ConfigureStartup.<>c__DisplayClass5_0.<ConfigureIceAuth>b__0(IOwinContext context, Func`1 next) in C:\_Releases\ICE\ICE3.2.400.16\Source\Framework\Epicor.RESTApi\Epicor.RESTApi\ConfigureStartup.cs:line 156
Has anyone seen these types of entries before, I’m wondering if I’ve missed (or messed up) a config somewhere.

No, you did not miss anything. Ms library now shows logging this way to avoid leaking of sensitive info.
Most probably your client sends ‘undefined’ instead of token to the server and this causes the error.

@Olga
Not really following

Do you mean whatever is firing the REST requests is not configured correctly?

Yes. It does not send valid jwt token

1 Like