• 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 ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
Bartenders:
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

Using secured and unsecured beans  RSS feed

 
Ranch Hand
Posts: 200
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

as described here (http://www.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?
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!