|
Home > Archive > WebSphere Application Server > September 2005 > Two logins to run app client
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Two logins to run app client
|
|
|
| Hi all,
Apologies for cross-posting from the Rational Application Developer forums, but hope I might get an answer from where since I didn't from there.
Having managed to get the Global Security set up in WebSphere (v6.0), with the application client logging in properly, I now have a problem with having to login twice to enter my application.
The first dialog is our normal application login dialog, which is used to authenticate against JAAS. The callback handler pops up the dialog when required, and authenticates ok.
The second dialog seems to be shown the first time a connection is made to the EJBs on the server. Having played around with sas.client.props, I can stop this dialog by setting the username and password in the sas.client.props file, but this is not ideal.
Is it possible to stop the second login dialog (the one initiated by websphere) without having to enter the username and password in the sas.client.props file?
| |
| Paul Ilechko 2005-09-20, 8:49 pm |
| lloyd.colling@dcstrans.com wrote:
> Hi all,
>
> Apologies for cross-posting from the Rational Application Developer
> forums, but hope I might get an answer from where since I didn't from
> there.
>
> Having managed to get the Global Security set up in WebSphere (v6.0),
> with the application client logging in properly, I now have a problem
> with having to login twice to enter my application.
>
> The first dialog is our normal application login dialog, which is
> used to authenticate against JAAS. The callback handler pops up the
> dialog when required, and authenticates ok.
>
> The second dialog seems to be shown the first time a connection is
> made to the EJBs on the server. Having played around with
> sas.client.props, I can stop this dialog by setting the username and
> password in the sas.client.props file, but this is not ideal.
>
> Is it possible to stop the second login dialog (the one initiated by
> websphere) without having to enter the username and password in the
> sas.client.props file?
Take a look here, see if you are doing things right in your client:
http://publib.boulder.ibm.com/infoc.../tsec_pacs.html
| |
|
| Cheers,
Looking at the documentation, it turns out that I have to initialise an InitalContext and lookup the jndi root at "" before doing the login, so that the login will affect both the application login and the connection login. No more WAS dialog! 
Thanks for your help
|
|
|
|
|