[
https://issues.jboss.org/browse/ELY-382?page=com.atlassian.jira.plugin.sy...
]
David Lloyd resolved ELY-382.
-----------------------------
Resolution: Rejected
On second thought, I'm rejecting this and throwing away the implementation.
The reason is that the callback handler is the thing which needs to track identity. The
{{ServerAuthenticationContext}} should be capturing the active {{SecurityIdentity}} on
instantiation, and maintaining an identity throughout the authentication process.
I will create a new JIRA, and a state machine diagram to illustrate the expected behavior
of the authentication context.
Add SASL server factory which has the ability to set a
SecurityIdentity during authentication tasks
---------------------------------------------------------------------------------------------------
Key: ELY-382
URL:
https://issues.jboss.org/browse/ELY-382
Project: WildFly Elytron
Issue Type: Task
Components: SASL
Reporter: David Lloyd
Assignee: David Lloyd
Add SASL server factory which has the ability to set a SecurityIdentity during
authentication tasks. This is necessary so that (for example) EXTERNAL can perform
authorization checks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)