• 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

JAAS

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
when i use a custom registry websphere is using LptaLoginModule to login the user (by invoking my registry class). this class creates its own principal, i suppose, which implements WSPrincipal. so whatever i try to propagate from client is ot taking effect. the one created at the server side is being used. i get the name of the user correctly from the pricipal but other information which i have in my custom principal is not propagated.

is it possible to write my own login module at the server side and change the security.xml file so that it is inovked not the LptaLogin module. is it the recommended approach in websphere?

is there any way to propagate my own principal to the server side.

i'm at wits end now.... please help.

thanks
Justin
 
reply
    Bookmark Topic Watch Topic
  • New Topic