• 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

"authenticate the caller" in exam objective

 
Bartender
Posts: 2418
13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
The exam objective says "authenticate the caller" for the implementing security objective.
But in JSR 318, it only covers authorization (method permission, declare roles, role link...).
I don't see any authentication in this specification. Maybe, getCallerPrincipal() is related to authentication.
 
Creator of Enthuware JWS+ V6
Posts: 3411
320
Android Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, you are right the emphasis is on authorization not on authentication.

You should know a bit about the EJBContext.getCallerPrincipal() in the different EJB types and what the the @RunAs annotation does with the authenticated user (e.g is the principal name still the same or not)

The obvious trick question related to this is whether the EJBContext.getCallerPrincipal() would return null or an empty Principal when the user is unauthenticated.
reply
    Bookmark Topic Watch Topic
  • New Topic