Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: handling user authorization failed #27

Closed
greenpau opened this issue Jan 24, 2022 · 1 comment
Closed

feature: handling user authorization failed #27

greenpau opened this issue Jan 24, 2022 · 1 comment

Comments

@greenpau
Copy link
Owner

A clear and concise description of what you want the system to do.

Currently, whether a user was previously authorized or whether the user wasn't authenticated, the user would get the same error:

2022/01/24 00:56:07.197 ERROR   http.handlers.authentication    auth provider returned error    {"provider": "authorizer", "error": "user authorization failed"}

There is a need to have different messages send to caddy.

@greenpau
Copy link
Owner Author

This is now resolved in v1.0.7 The message identifies a user by IP, as well as by the provided metadata in a token.

  2022/01/28 01:54:25.220 ERROR   http.handlers.authentication    auth provider returned error    {"provider": "authorizer", "error": "user authorization failed: src_ip=10.0.2.2, src_conn_ip=10.0.2.2, jti=NZbUxiUWBzqgCSSS97lXlFP1eJGJLkybsMhwcBHMC1, sub=webadmin, email=webadmin@localdomain.local, reason: user role is valid, but not allowed by access list"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant