• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

wesbsphere pluggable client & JAAS

 
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I am using Websphere Pluggable Client version 5.1.1.2 from 16.11.2004 against Websphere AS 5.1.1.2 from 16.11.2004.

Programmatic login with Java Authentication and Authorization Service is not working any more as it did. The problem appears to be in the initalization of the SecurityServer:

--------
"Error: Login exception com.ibm.websphere.security.auth.WSLoginFailedException: SECJ0395E: Could not locate the SecurityServer at host/port:xxx.yyy.zzz.187/9909 to validate the userid and password entered. You may need to specify valid securityServerHost/Port in (WAS_INSTALL_ROOT)/properties/sas.client.props file.
Authetication failed!".
--------

It seems that some SecurityServer host/port are suddenly required and they are initialized to some bogus value. If the properties:
com.ibm.CORBA.securityServerHost
com.ibm.CORBA.securityServerPort

are written in sas.client.props the Pluggable Client takes them into account.
Problems is that the our code initializes the SecurityServer using the code below:

/******************************/
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL,
"corbaloc:iiop:myhost.mycompany.com:2809");
Context initialContext = new InitialContext(env);
Object obj = initialContext.lookup("");
/******************************/

This initialization is ignored and the SecurityServer is always searched at the:
com.ibm.CORBA.securityServerHost
com.ibm.CORBA.securityServerPort
is they have been set. If they haven't the Client just searches for SecurityServer on some "best-guess" port on the localhost.

Any ideas, knowledge how to bypass that, info about fixes?

Thanks,
Cristian

PS: This look a little bit like problem PQ93263.
 
reply
    Bookmark Topic Watch Topic
  • New Topic