[
https://issues.jboss.org/browse/ELY-268?page=com.atlassian.jira.plugin.sy...
]
Darran Lofthouse resolved ELY-268.
----------------------------------
Resolution: Out of Date
Marking as out of date as most mechanisms are now implemented and the remainder are being
implemented now.
APIs and integration are being massaged as the final ones come through.
Review how mechanisms meet HttpAuthenticator
--------------------------------------------
Key: ELY-268
URL:
https://issues.jboss.org/browse/ELY-268
Project: WildFly Elytron
Issue Type: Sub-task
Components: HTTP
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.1.0.Beta6
The current implementation is using a
Supplier<List<HttpServerAuthenticationMechanism>> when get is called on this
Supplier a ServerAuthenticationContext needs to be created, then all possible mechanisms
need to be queried before the list of mechanisms is created.
The HTTP Authenticator is created per request. API may be fine but we may need an easier
way to provide all the mechanisms.
Will look at that one later once hot deployment is also considered fully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)