You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rémy Lesiak (JIRA)" <ji...@apache.org> on 2010/11/10 14:25:22 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=63237#action_63237 ]
Rémy Lesiak commented on AMQ-2456:
----------------------------------
James,
I made the test with Activemq 5.4.1 but this doesn't work.
cheers,
Rémy.
> 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
> Assignee: Dejan Bosanac
> Priority: Minor
> Fix For: 5.4.0
>
> 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.