[ 
https://issues.apache.org/jira/browse/QPIDJMS-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413076#comment-17413076
 ] 

ASF GitHub Bot commented on QPIDJMS-548:
----------------------------------------

michaelandrepearce opened a new pull request #43:
URL: https://github.com/apache/qpid-jms/pull/43


   Add mapping from jndi principle and credentials to username and password for 
the default connection factory when using provider url 
   Add test case


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


> Support using principle and credentials from jndi context for default CF when 
> using naming url
> ----------------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-548
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-548
>             Project: Qpid JMS
>          Issue Type: Improvement
>          Components: qpid-jms-client
>            Reporter: Michael Andre Pearce
>            Priority: Major
>             Fix For: 1.2.0
>
>
> Since QPIDJMS-542 it possible to provide the url on the context via 
> java.naming.provider.url, as an extension / enhancement to this would be to 
> support using the jndi context security principle and security context.
> e.g.
> java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
> java.naming.provider.url=failover:(amqps://host1:5672,amqps://host2:5672)
> java.naming.security.principal=myuser
> java.naming.security.credentials=mypassword
>  
> Would set the user and password on the connection factory to "myuser" and 
> "mypassword" 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to