Skip to content

Conversation

@jzheaux
Copy link
Owner

@jzheaux jzheaux commented Aug 13, 2025

No description provided.

jzheaux added 15 commits August 12, 2025 17:10
Oftentimes, a filter has its own authentication manager or it
has something specific that it needs to do regarding authentication
that is independent of a shared authentication manager.

Allowing the authentication manager to be post-processed allows
an application to apply authentication-mechanism-specific
post-processing to the authentication request and result.
There are a number of scenarios where it's desireable to update the
authorities in an authentication after identity has already been established.

For example, if a second factor is required or if temporary
authorization is needed for a given page, these likely won't
update the principal; they simply need to add more authorities
to the existing authentication.
This is a handy implementation that allows an entry point to
operate differently when there is already a known user in
context. In some cases, it is not desireable to show the
end user another form and ask them for their username when
we already know it, for example.
When access is denied, if we have a way to obtain the missing
authorities, this class allows that way to be specified.
This update allows AuthoritiesAuthorizationManager to operate
in either and or or mode, given a list of authorities.
A configurer that extends the ability of any authentication configurer
to participate as an additional authentication factor
Allowing individual authorities to expire offers enormous flexibility
as far as granting authorities that need to be renewed independently
from logging in.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant