Home > Archive > Java Help > February 2006 > Re: Accessing an EJB from a standalone client when websphere security
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 |
Re: Accessing an EJB from a standalone client when websphere security
|
|
| Paul Ilechko 2006-02-18, 6:58 pm |
| regis.decamps@banque-france.fr wrote:
> Hi,
>
> A client running on WSAD 5 (or Websphere Thin Application Client) tries
> to open a connection on Websphere 5.0 with security enabled (and Java 2
> security disabled).
>
You need to do a JAAS programmatic login, see here:
http://publib.boulder.ibm.com/infoc.../tsec_pacs.html
>
| |
| Paul Ilechko 2006-02-20, 7:00 pm |
| regis.decamps@banque-france.fr wrote:
> I really wonder how to pass the identity to the server (accessID: null
> is not granted any of the required roles). Do you know how to perform
> this action with the Universal Test Client, by the way. I'd like to
> have a way to know which of my client or my server is broken.
A couple of questions ...
1. Do SECURITY_PRINCIPAL and SECURITY_CREDENTIALS contain a valid userid
and password for your user registry?
2. Have you mapped this user, or a group that contains this user, to the
role that is required to call the EJB ?
Paul.
| |
| Paul Ilechko 2006-02-21, 7:03 pm |
| regis.decamps@banque-france.fr wrote:
> Do you have any other suggestion?
Can you call the EJB from the main thread in your client rather than
creating a new thread ?
|
|
|
|
|