[
https://issues.jboss.org/browse/ELY-257?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on ELY-257:
---------------------------------
The intention is that the user must write a callback handler to handle the various
callbacks that may be presented. If an intermediate layer (like a protocol layer)
determines that certain pieces of information fall under its control, rather than the
user's (for example, channel binding or SSL socket information), then it can use the
facade factories to intercept those particular pieces of information, while passing the
rest on to the user. A layer may also enhance the authentication mechanism in other ways
using other facade classes from the {{util}} package.
Hopefully this answers the question.
Allow usage of properties to configure sasl server factories
------------------------------------------------------------
Key: ELY-257
URL:
https://issues.jboss.org/browse/ELY-257
Project: WildFly Elytron
Issue Type: Feature Request
Components: SASL
Reporter: Kabir Khan
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.1.0.Alpha2
There is some discussion on
https://github.com/wildfly-security/wildfly-elytron/pull/264.
In this case the issue is that we have a ChannelBindingSaslServerFactory (and same for
client) which provides a callback handler to deal with the channel binding callbacks
needed by Gs2SaslServerFactory and Gs2SaslClientFactory. This is fine for when people
create their own SaslServerFactory, and use that to create a SaslServer.
However, if they want to call Sasl.createServer()/.createClient() they need to provide
their own callback handler to deal with the channel binding types.
One option would be to allow the usage of properties for this configuration needed by the
factories.
However, having slept on it, the callback handler passed in to Sasl.createXXX() would
need to handle all callbacks. Is there a way to get a 'real' callback handler for
a user wishing to instantiate clients/servers this way? Or is the intent that they have to
write their own CBH?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)