You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "James Casey (JIRA)" <ji...@apache.org> on 2010/05/17 11:59:04 UTC
[jira] Commented: (AMQ-2456) New Authentication plugin :
JaasDualAuthentcationPlugin/Broker
[ https://issues.apache.org/activemq/browse/AMQ-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59386#action_59386 ]
James Casey commented on AMQ-2456:
----------------------------------
Hi,
could a commiter have a look at this patch and see if it's ok to commit. We've been running it in production for a while now and it shows no problems (and is useful).
cheers,
James.
> New Authentication plugin : JaasDualAuthentcationPlugin/Broker
> --------------------------------------------------------------
>
> Key: AMQ-2456
> URL: https://issues.apache.org/activemq/browse/AMQ-2456
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.3.0
> Reporter: James Casey
> Priority: Minor
> Attachments: dualauthbroker.patch
>
>
> Find attached a new authentication plugin which uses different JAAS authentication domains depending if the connection is SSL enabled or not.
> This allows for clean separation of authentication polices depending on connection type - e.g. always authentication via the DN if SSL and authenticate using username/password (or login all anonymous users as guests) if using a non-SSL connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.