Hi everybody,

I'm facing a severe JAAS-problem. This is my core-code block:

callback = new WSCallbackHandlerImpl ("user",password");
LoginContext lc = new LoginContext("WSLogin",callback);
lc.login();
Subject subject = lc.getSubject();
Iterator principals = subject.getPrincipals().iterator();
while (principals.hasNext())
{
System.out.println("secureCall() : ############################") ;

Principal tmp = (Principal) principals.next();
System.out.println("secureCall() : List Principals : name is " + tmp.getName());

System.out.println("secureCall() : ############################") ;

}
WSSubject.setRunAsSubject(subject);

The problem is, the subject does not contain any principals. There's no error-message on the client-side. All parameter are set:

-Djava.security.policy=config/security.policy
-Djava.security.auth.login.config=file:config/wsjaas.conf
-Dcom.ibm.SSL.ConfigURL=file:config/ssl.client.props
-Dcom.ibm.CORBA.ConfigURL=config/sas.client.props
(or -Dcom.ibm.CORBA.ConfigURL=file:/config/sas.client.props , I tried both)

If I turn off security on the server-side, the code works fine even when I remove the ConfigURL from JVM-settings! It looks like the sas.client.props is ignored completely!

Any suggestions? How can make the client JVM tell me if sas.client.props are looaded?

I' m desperatly looking for clues....

harry