[
https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy...
]
Pedro Igor commented on ELY-428:
--------------------------------
Wouldn't the deployer be specific to Keycloak-SSO subsystem and to the Console SSO Use
Case ?
My point is not really specific to WFLY but to any web container we support in
elytron-web.
Beside that, IIRC, elytron-keycloak will replace Keycloak WildFly/Undertow Adapters once
we have ELY fully integrated with the application server. Which will provide a much better
integration with the server and solely based on ELY APIs. In this case, we must be able to
support a eager approach to initialization.
I've in my session notes a minor change to the
```HttpServerAuthenticationMechanismFactory``` to allow the factory to put things in the
application scope (such as the config) during the configuration of the security handler.
So we could just grab these things from authentication mechanisms when actually evaluating
a request.
HTTP Mechanism configuration during deployment
----------------------------------------------
Key: ELY-428
URL:
https://issues.jboss.org/browse/ELY-428
Project: WildFly Elytron
Issue Type: Enhancement
Components: HTTP
Affects Versions: 1.0.2.Final
Reporter: Pedro Igor
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.1.0.Beta5
It should be possible to configure a HTTP mechanism during deployment in order to
parse/load configuration and reuse it in subsequent requests to an application.
The most common use case for that is around mechanisms that need to read some
configuration from inside a deployment (or provided by the mech config) when it is being
deployed to the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)