Project

General

Profile

Actions
Copy link

Task #3341

open

Improve debugging for failing CAS authentication

Added by Petr Fišer about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/20/2023
Due date:
% Done:

0%

Estimated time:
Owner:

Description

When we use IdM together with CAS AM, IdM authentication handler doesn't log anything if there is a problem in backend calls between IdM and CAS.
This makes situations like network connectivity problems, certificate issues, etc. very hard to debug because we do not have any information to begin with.

  • It would be awesome if IdM logged at least something like: "connection refused", "certificate problem", "403 from upstream".
  • It should not be whole stacktrace as there is a risk of huge amount of logs being generated.
  • It probably should not be tied to user requests and/or backend calls between CAS and IdM. If we did that, anybody could DoS the IdM by making repeating requests and eating up disk space with bloated application log.

No data to display

Actions
Copy link

Also available in: Atom PDF