Refactor #30699
Error logging for invalid token is misleading
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Authentication
Target version:
-
Pull request:
Fixed in Releases:
Found in Releases:
Description
Logging error for broken or expired JWT should not use error level, it's expected error, so it should probably use warning. https://github.com/theforeman/foreman/blob/f4b4ab58fe8ea4f8000179ff6fde8dadfc0042c1/app/services/sso/jwt.rb#L15-L20
Related issues
Associated revisions
History
#1
Updated by Marek Hulán almost 2 years ago
- Related to Feature #30440: Simple & automatic host registration WF added
#2
Updated by Jaskaran Singh Narula over 1 year ago
- Pull request https://github.com/theforeman/foreman/pull/8296 added
#3
Updated by The Foreman Bot over 1 year ago
- Status changed from New to Ready For Testing
#4
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 2.5.0 added
#5
Updated by Jaskaran Singh Narula over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|76fec17eeeda4cb6ca75b788c48e58d5d99be746.
#6
Updated by Tomer Brisker over 1 year ago
- Category set to Authentication
Fixes #30699 - Log invalid JWT at warning instead of error