xxx-jboss-beans.xml realm

[michel.strogoff]

Hi,

I have created a realm configuration to authenticate users against a JNDI registered database.

I have followed the instructions of this blog : http://anil-identity.blogspot.com/2009/05/as5-specifying-security-domain.html.

The configuration of the realm seems to be correct since it works correctly when I put it in the login-config.xml file.

But when I use it as a embedded in my web app (along with jboss-web.xml file), I get the following error :

javax.security.auth.login.LoginException: Error looking up DataSource from: java:/jdbc/ShareDataSource

at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:194)
at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

...

Caused by: javax.naming.NameNotFoundException: ShareDataSource

When I connect to JBoss admin-console, I can see the data source is available. And the application starts up and connects to it.

But the realm login module is not.

Can you see why ?

Best regards,
Eric

[jaikiran]

Post the contents of your -ds.xml and also the jboss-web.xml.

While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

[wolfgangknauf]

Hi Eric,

any newlines/spaces around the datasource name? I run into a similar problem recently and found that "login-config.xml" trims the JNDI name, but the new -jboss-beans.xml does not.

Hope this helps

Wolfgang

[michel.strogoff]

Hi guys,

Thank you for your answers. You were right Wolfgang !

I had applied xml text formatting with eclipse to my xxx-jboss-beans.xml file, and it caused a blank line to be appended to the source name. I couldn't see it in the log since blank character are not visible !

Thnak you very much,
Best regards,
Eric

[wolfgangknauf]

I filed https://jira.jboss.org/jira/browse/SECURITY-421 , because I think this is a nasty trapdoor and should be fixed.

Wolfgang