Throw an error and stop login if NATS is not reachable #5

Open
opened 2025-05-06 12:11:06 +02:00 by pb · 0 comments
Owner

After a crash of the host and a restart in docker mode, oc-auth was not able to create well formatted token. Looking at the container log the only error was that the NATS container was not reachable.
However the /login route did return a token, which didn't contain any claims.
In the keto container I have been able to identify two errors in the hydra container:

  • A request failed because configuration key "urls.consent" is missing or malformed
  • A request failed because configuration key "urls.login" is missing or malformed

I suggest that we return an explicit error when this happens so that we can identify it more quickly

After a crash of the host and a restart in docker mode, oc-auth was not able to create well formatted token. Looking at the container log the only error was that the NATS container was not reachable. However the /login route did return a token, which didn't contain any claims. In the keto container I have been able to identify two errors in the hydra container: - A request failed because configuration key "urls.consent" is missing or malformed - A request failed because configuration key "urls.login" is missing or malformed I suggest that we return an explicit error when this happens so that we can identify it more quickly
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: core/oc-auth#5
No description provided.