From 560bba622c3fc8e6c9b9f13941ad74c22560f938 Mon Sep 17 00:00:00 2001 From: dab246 Date: Thu, 15 Feb 2024 14:18:56 +0700 Subject: [PATCH] TF-2592 Add adr for issue #2592 Signed-off-by: dab246 --- ...-handling-on-no-longer-valid-oidc-token.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/adr/0034-error-handling-on-no-longer-valid-oidc-token.md diff --git a/docs/adr/0034-error-handling-on-no-longer-valid-oidc-token.md b/docs/adr/0034-error-handling-on-no-longer-valid-oidc-token.md new file mode 100644 index 000000000..57048d60a --- /dev/null +++ b/docs/adr/0034-error-handling-on-no-longer-valid-oidc-token.md @@ -0,0 +1,19 @@ +# 34. Error handling on no longer valid OIDC token (Issue #2592) + +Date: 2024-02-15 + +## Status + +Accepted + +## Context + +- When my OIDC token is expired, I see an awful red error message while being redirected + +## Decision + +- When my OIDC token is expired, I am just redirected to the OIDC provider portal. No need to show an awful error. + +## Consequences + +- In case of receiving a `BadCredentials` error, the system automatically logs out and returns to the login screen without any notification to the user. \ No newline at end of file