Is it still possible to package DB and LDAP configuration information in your
web app and have JBoss use that upon application deployment? Or is the only
way to do this by adding (in my case) oracle-ds.xml to the server's deployment
directory, and adding a policy to the login-config.xml?
Here'
It makes sense, I just don't have time to learn EJB right now. I don't like
the fact that I'll have to create different EJBs to incorporate different user
stores (realms), but if that's how it has to be done, we'll get to it
eventually.
I agree that, since JAAS can't be used, creating the EJBs
So there is no way to avoid having webapp code explicitly pointing at LDAP?
I was thinking of a workaround where I would store the LDAP connect info in the
web.xml somewhere, and then read that into an object and bind it to some JNDI
address, but I still don't like that solution. I'd still have
cgriffith,
I would like my web app to get the usernames from JAAS, so that no matter what
the policy in use at the time the web app is running, it will use whatever
policy is set. If I do what you said, and create a layer between the app and
LDAP, I'm still going directly to LDAP. That's what
cgriffith,
I agree that the use of reflection there is really bad. As I said, I didn't
write it, and wouldn't. It works in Tomcat, but it seems really wrong.
It sounds like you are saying that web apps shouldn't be able to get a list of
users that are in a specific role from the application s
I'll preface this post by saying that I'm new to J2EE. My problem is that some
of our code that ran on Tomcat 5.0.28 doesn't work on JBoss 4.0.3CR2.
Principal p = request.getUserPrincipal();
This code in Tomcat 5.0.28 returned a principle that we could use to
reflectively invoke 'getRealm' to
