| 2017-10-24 07:44:02 |
Colleen Murphy |
description |
When things go wrong and the regular info-level logs are not informative enough, it is common to turn on debug logging to see what's up. When we do that, we see this message spamming the logs for auth requests:
"There is either no auth token in the request or the certificate issuer is not trusted. No auth context will be set."
It's actually a benign message but it's meaning is totally unclear and to the untrained eye it looks like the cause of auth problems. We should either get rid of the message or reword it to make it clear what it means.
It looks like it's perhaps a holdover from the PKI days and could just be removed but I'm not sure. |
When things go wrong and the regular info-level logs are not informative enough, it is common to turn on debug logging to see what's up. When we do that, we see this message spamming the logs for auth requests:
"There is either no auth token in the request or the certificate issuer is not trusted. No auth context will be set."
It's actually a benign message but its meaning is totally unclear and to the untrained eye it looks like the cause of auth problems. We should either get rid of the message or reword it to make it clear what it means.
It looks like it's perhaps a holdover from the PKI days and could just be removed but I'm not sure. |
|
