activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3924) Allow REST API to connect to the secured broker
Date Thu, 12 Jul 2012 11:08:33 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac resolved AMQ-3924.
--------------------------------

    Resolution: Fixed

Fixed with svn revision 1360626.

You can now specify basic auth user/pass and that will be used when creating JMS connection.
Example

{code}curl -u system:manager -d "body=message" http://localhost:8161/demo/message/TEST?type=queue{code}
                
> Allow REST API to connect to the secured broker
> -----------------------------------------------
>
>                 Key: AMQ-3924
>                 URL: https://issues.apache.org/jira/browse/AMQ-3924
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.6.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.7.0
>
>
> We should be able to connect to the secured broker using REST API. The idea mechanism
for that would be reusing Authorization header in HTTP request that is used to secure web
servers. The format of the header is
> Authorization: Basic base64(username:password)
> and that could be supplied by turning on basic auth on Jetty, or set directly by the
http client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message