You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our authproc processing in AuthProcService->processState() is missing some features from the main ProcessingChain. If an authproc needs to redirect the user somewhere (for consent, mfa, etc) then there is no easy way to resume the processing from the next filter. The ProcessingChain class used by SSP allows for resuming by storing the not-yet processed filter in the $state.
I think wrapping ProcessingChain from AuthProcService would allow us to use authproc filters that perform redirects.
The text was updated successfully, but these errors were encountered:
I also have a use case for an interactive authproc (MFA with the simplesamlphp-module-webauthn). Being able to run interactive authprocs would be a very valuable addition.
When I did similar work for the authoauth2 module it was not as complicated as I was expecting. Most of that PR is documentation and testing, and maybe a dozen lines for the authproc method.
Our authproc processing in
AuthProcService->processState()
is missing some features from the mainProcessingChain
. If an authproc needs to redirect the user somewhere (for consent, mfa, etc) then there is no easy way to resume the processing from the next filter. TheProcessingChain
class used by SSP allows for resuming by storing the not-yet processed filter in the$state
.I think wrapping
ProcessingChain
fromAuthProcService
would allow us to use authproc filters that perform redirects.The text was updated successfully, but these errors were encountered: