Originally posted by Kyle Brown:
I can't imagine anyone else would try this. This is (as you've found out) a really, really bad idea. I would like to know some of the reasons why you think you need to do this. What could you be doing that you couldn't accomplish by installing your apps on some other server and then making JMX calls into the deployment manager?
Kyle
Sorry I waited so long to reply. I'm back to working on this issue, and I'm willing to try making remote calls to the deployment manager. Do you know whether it's possible to forward credentials when using admin APIs. My application consists of a web service, which is authenticated using basic auth. This web service then makes calls to the AdminService (will change to use AdminClient), ConfigService, and AppManagement APIs. If I'm doing this remotely in a secure environment, what's the best way to forward the credentials to the deployment manager via these APIs? It would be unfortunate if I had to pass the user name and password as parameters to the web service. The WebSphere docs claim that when using LPTA, credentials are forwardable. Does this apply to the admin APIs?
Thanks,
Geoff