[
https://issues.apache.org/activemq/browse/AMQ-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62700#action_62700
]
James Casey commented on AMQ-2456:
----------------------------------
Remy,
we've checked on our installations here and they work ok in this configuration
- but they are FUSE 5.3.2 version, not the activemq one.
I think there is another bug which was fixed shortly after 5.3.2 was released
that you're hitting - AMQ-2449.
Could you try this with a more recent broker (5.4 ?) or apply the patch from
AMQ-2449 as well.
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
> 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.
