[
https://issues.apache.org/jira/browse/QPIDJMS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742344#comment-15742344
]
Timothy Bish commented on QPIDJMS-232:
--------------------------------------
Current plan would be to not send the open frame until the start method or
client id is set as that is necessary for the JMS API compliance bit of the JMS
client.
> Perform Authentication when the remote connection is established instead of
> waiting until Connection start
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-232
> URL: https://issues.apache.org/jira/browse/QPIDJMS-232
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.11.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.20.0
>
>
> Instead of waiting until the connection is started to perform authentication
> we should perform the SASL authentication if available when the connection is
> established. This allows the createConnection methods in the
> ConnectionFactory to fail fast instead of waiting until the Connection is
> later started or a client ID is set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
