[
https://issues.apache.org/jira/browse/FALCON-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921160#comment-13921160
]
Jean-Baptiste Onofré commented on FALCON-230:
---------------------------------------------
By the way, with the current patch, it's possible to use encrypted password:
instead of using the password in clear, you can use the ENC prefix:
{code}
ENC(mYRkg+4Q4hua1kvpCCI2hg==)
{code}
I can propose a new patch that allow:
- to use the username/password in the cluster definition (with ENC) support (as
it is in the current patch)
- to use conf/activemq-credential.properties to store username/password (again
with ENC support for password): Falcon can look for this file
- to use Kerberos, using a broker URI like https://localhost:61616?auth=KRB (it
requires to update at least to ActiveMQ 5.6.0).
Does it sound good to you ?
> Add broker authentication support
> ---------------------------------
>
> Key: FALCON-230
> URL: https://issues.apache.org/jira/browse/FALCON-230
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Venkatesh Seetharam
> Assignee: Jean-Baptiste Onofré
> Fix For: 0.5
>
> Attachments: FALCON-230.patch
>
>
> I'm leaving it here for the sake of completeness. Topics might need
> authorization and not sure how to do it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
