Dimitrij Drus issues

Results 90 issues of


                                            Dimitrij Drus

wip: Multiple principals for a Subject

## Related issue(s) closes #921 ## Checklist - [x] I agree to follow this project's [Code of Conduct](../CODE_OF_CONDUCT.md). - [x] I have read, and I am following this repository's [Contributing...

Configurable maximum size for the in-memory cache

### Preflight checklist - [X] I agree to follow this project's [Code of Conduct](https://github.com/dadrus/heimdall/blob/main/CODE_OF_CONDUCT.md). - [X] I have read and am following this repository's [Contribution Guidelines](https://github.com/dadrus/heimdall/blob/main/CONTRIBUTING.md)." - [ ] I...

feature

Authorizer for access token verification

feature

Support for API-Key based authentication

feature

Consider applicability of https://github.com/expr-lang/expr

good first issue

research

Consider migration from ZeroLog to slog

research

Support the configuration of credentials verified by basic auth authenticator in PHC format

... including the support for argon2, scrypt, bcrypt and pbkdf2 to increase security. Thus way this authenticator will not only be resistant against side channel attacks (implemented today), but also...

good first issue

feature

Add suport for validation of Certificate-Bound Access Tokens according to RFC 8705

In principle this can be achieved already today by making use of the `local` authorizer and checking the presence of the `cnf` (confirmation) claim holding the required certificate hash and...

feature

Implement oidc client functionality

This would allow usage of heimdall without additional infrastructure components, like [oauth2-proxy](https://oauth2-proxy.github.io/oauth2-proxy/) or [lua-resty-openidc](https://github.com/zmartzone/lua-resty-openidc) in environments where the oidc protocol is "misused" in a sense, that the oidc client and...

feature

Implement authorizer, which would enable usage of X509 Certificates in an mTLS context

Compared to #155, this feature will not derive the subject from the certificate, but rather make the certificate properties available for authorization purposes. E.g. values from extensions like PolicyOID, or...

feature