This week's book giveaway is in the Server-Side JavaScript and NodeJS forum.
We're giving away four copies of Micro Frontends in Action and have Michael Geers on-line!
See this thread for details.
Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

How to set the User Principal

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have the next scenario:

Browser is sending HTTP request, which activates a controller on the WAS.

When calling: WSSubject.getCallerPrincipal, request.getUserPrincipal, request.getRemoteUser I have the user that activated the http request.

I need from the controller to activate a new HTTP request to another WAS (currently, it will be the same WAS, but will be separated in the future).

I want that the user principal of the first request will be transferred as the user principal of the second call.

Is it possible?

If not - I can workaround it, it I can define an application user that will always be the activated user, but now also that doesnt work - since I am getting null for the user principal in the second activation.

Thank You.
The moth suit and wings road is much more exciting than taxes. Or this tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic