[jboss-jira] [JBoss JIRA] Commented: (JBASM-23) multiple servers with different credentials

[Aleksandar Kostadinov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBASM-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444010#action_12444010 ] 

Aleksandar Kostadinov commented on JBASM-23:
--------------------------------------------

Hallo, Anil. First thank you for your reply.
I see that the "server" property is false by default. And setServer() method makes it true. So actually here the problem is not that we want single credentials for all servers but rather different credentials for the different servers.

Would you be able to explain or point me at documentation how to make certain calls with certain credentials? 
For example I want to invoke an mbean operation with this username/password pair then operation on another server's mbean with different credentials.

[code]
doAs(credsServer1);
invoke(...);
doAs(credsServer2);
invoke(...);
[/code]

Or something similar? To be clear it's not guaranteed invokes will be done by a different or the same thread.

I can see that if I SecurityAssociation.setServer() then I can create a controlling thread for every server and pass operations through it. But I hope there will be some more lightweight solution to the problem.

Thanks again!

> multiple servers with different credentials
> -------------------------------------------
>
>                 Key: JBASM-23
>                 URL: https://jira.jboss.org/jira/browse/JBASM-23
>             Project: JBoss AS Server Manager
>          Issue Type: Task
>    Affects Versions: 1.0.0.GA
>            Reporter: Aleksandar Kostadinov
>            Assignee: Aleksandar Kostadinov
>            Priority: Minor
>
> Currently server manager sets credentials like 
>            SecurityAssociation.setPrincipal(new SimplePrincipal(username));
>            SecurityAssociation.setCredential(password);
> I think that in this case every managed server should use the same credentials. Probably using the JndiLoginInitialContextFactory can fix that but not for the http invoker.
> Alternative way with JAAS needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira