You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/08/11 22:51:46 UTC
[jira] [Commented] (DISPATCH-152) Expose SASL-related data via
management
[ https://issues.apache.org/jira/browse/DISPATCH-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682480#comment-14682480 ]
ASF subversion and git services commented on DISPATCH-152:
----------------------------------------------------------
Commit 1695375 from [~tedross] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1695375 ]
DISPATCH-152, DISPATCH-153
- Expose SASL/SSL capabilities via the configuration schema
- Provide instrumentation on connections to expose security data
- Updated the tooling (qdstat -c) to display the new data
- Updated the tests to conform to the security changes
- Bumped the shared-object major version
> Expose SASL-related data via management
> ---------------------------------------
>
> Key: DISPATCH-152
> URL: https://issues.apache.org/jira/browse/DISPATCH-152
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.5
>
>
> Now that SASL is integrated into DIspatch, the new SASL data needs to be made accessible from management:
> - Mechanism in effect
> - Authenticated user in effect
> - Authentication in effect (i.e. is the user authenticated)
> - Encryption in effect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org