activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rémy Lesiak (JIRA) <j...@apache.org>
Subject [jira] Commented: (AMQ-2456) New Authentication plugin : JaasDualAuthentcationPlugin/Broker
Date Mon, 11 Oct 2010 16:22:42 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62496#action_62496
] 

Rémy Lesiak commented on AMQ-2456:
----------------------------------

Hi James,

I use Activemq 5.3.2 with the patch.

The xml configuration of my server broker :
    <transportConnectors>
...
      <transportConnector name="SSLArchiver" 
                          uri="ssl://10.90.xx.xx:61700?needClientAuth=true&amp;transport.enabledCipherSuites=TLS_DHE_RSA_WITH_AES_256_CBC_SHA"/>
...
    </transportConnectors>

The xml configuration of my client broker when it's work :
    <networkConnectors>
        <networkConnector
            name ="gsb-archivage-${hostname}"
            uri="static:(ssl://10.90.xx.xx:61700)"
            duplex="false"
         />
    </networkConnectors>

The xml configuration of my client broker when it's not work :
    <networkConnectors>
        <networkConnector
            name ="gsb-archivage-${hostname}"
            uri="static:(ssl://10.90.xx.xx:61700)"
            duplex="true"
         />
    </networkConnectors>

Thanks!


> 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.


Mime
View raw message