• 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

Using secured and unsecured beans

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

as described here (https://coderanch.com/t/620676/JBoss/Custom-Login-Module-EAP-JBoss) we use a custom login module within JBoss EAP. Now I'm facing some problems when invoking an EJB that is not part of the security domain.

Short config from standalone-full.xml:

Security realms


Ejb3


Remoting


SecurityDomain


If I don't change ApplicationRealm to my own realm, our LoginModule is not invoked!

We have beans with



and beans without that annotation.

What we want to archieve is, that we can invoke some beans without being an authenticated user. Do we have a chance to do this? Or do I have to use some dummy user for those beans? (That would mean to user two different users in my client application. The user [identified by username and password] himself and the dummy user. So I'd need two different login contexts. (??)

Any hints?
reply
    Bookmark Topic Watch Topic
  • New Topic