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 t
he 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 au
thenticate against JAAS. The callback handler pops up the dialog when requir
ed, and authenticates ok.

The second dialog seems to be shown the first time a connection is made to t
he EJBs on the server. Having played around with sas.client.props, I can sto
p this dialog by setting the username and password in the sas.client.props f
ile, but this is not ideal.


Is it possible to stop the second login dialog (the one initiated by websphe
re) without having to enter the username and password in the sas.client.prop
s file?

[ Post a follow-up to this message ]

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

[ Post a follow-up to this message ]

Cheers,

Looking at the documentation, it turns out that I have to initialise an Init
alContext 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 m
ore WAS dialog! 

Thanks for your help

[ Post a follow-up to this message ]