ERROR: failed to configure authentication processes: failed to unmarshal OpenID Connect .well-known metadata: invalid character 'I' looking for beginning of value #1210
Comments
|
You're correct, there was an incident that appears to have caused an issue with the OICD endpoint used by the CLI (I myself just ran into this). The endpoint is back up already but I'll leave this issue open for now until I get a confirmation that the underlying issue is confirmed resolved. Thanks! |
|
@Integralist looking good now, thanks! I'm wondering if that's an opportunity to catch that type of error and improve the message (e.g.: if a 5xx is returned then switch the message to "An unexpected authentication error occurred, check http://fastlystatus.com for any possible incidents" and then some debug details (e.g.: statuscode/body)). Happy to work on an MR for that if the behaviour is desired. In any case, I'll close this issue since the original problem is resolved. |
Yes please! That would be very much appreciated 🙂 🙇🏻 |
When Fastly servers are unresponsive (indicated by a 5xx response), the CLI currently shows a cryptic error message due to unexpected values in the response body (e.g., unable to parse body as JSON). The last incident caused the CLI to display: > ERROR: failed to configure authentication processes: failed to unmarshal OpenID Connect .well-known metadata: invalid character 'I' looking for beginning of value The 'I' referred to the "Internal Server Error" in the response body, which is unclear/unactionable from a user perspective. This change introduces a validation to handle this specific scenario: If the authentication request returns a 5xx status code, it is now recognized as an error. The CLI will display a more actionable message, informing clients that the error is likely due to an outage or incident on the Fastly side. Clients can then check the status page or contact support. Context: * fastly#1210 * https://www.fastlystatus.com/incident/376536
When Fastly servers are unresponsive (indicated by a 5xx response), the CLI currently shows a cryptic error message due to unexpected values in the response body (e.g., unable to parse body as JSON). The last incident caused the CLI to display: > ERROR: failed to configure authentication processes: failed to unmarshal OpenID Connect .well-known metadata: invalid character 'I' looking for beginning of value The 'I' referred to the "Internal Server Error" in the response body, which is unclear/unactionable from a user perspective. This change introduces a validation to handle this specific scenario: If the authentication request returns a 5xx status code, it is now recognized as an error. The CLI will display a more actionable message, informing clients that the error is likely due to an outage or incident on the Fastly side. Clients can then check the status page or contact support. Context: * fastly#1210 * https://www.fastlystatus.com/incident/376536
…ve (#1212) * Handle Fastly API unresponsiveness Errors on Authentication When Fastly servers are unresponsive (indicated by a 5xx response), the CLI currently shows a cryptic error message due to unexpected values in the response body (e.g., unable to parse body as JSON). The last incident caused the CLI to display: > ERROR: failed to configure authentication processes: failed to unmarshal OpenID Connect .well-known metadata: invalid character 'I' looking for beginning of value The 'I' referred to the "Internal Server Error" in the response body, which is unclear/unactionable from a user perspective. This change introduces a validation to handle this specific scenario: If the authentication request returns a 5xx status code, it is now recognized as an error. The CLI will display a more actionable message, informing clients that the error is likely due to an outage or incident on the Fastly side. Clients can then check the status page or contact support. Context: * #1210 * https://www.fastlystatus.com/incident/376536 * fix(app): use %d for int type * fix(app): read body for use in error response * refactor(app): use http constant * fix(app): write valid code --------- Co-authored-by: Marcelo Boeira <marcelo@boeira.me>
Version
What happened
We have a pipeline, that hasn't changed in a while, with this command:
It normally publishes the application to compute @ edge, now it started failing with:
Note: It seems to be related to https://www.fastlystatus.com/incident/376536, I'm guessing the
invalid character 'I' looking for beginning of valueis forInternal Server Errorbut thought of reporting it here should other people face it too.The text was updated successfully, but these errors were encountered: