[Design of Security on JBoss] - inconcistency between security-config_5_0.xsd and xml tests
by alex.loubyansky@jboss.com
The problem is in the authentication-jaspi element which is declared in the XSD as
| <xsd:element name="authentication-jaspi">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:skip/>
| </xsd:appinfo>
| </xsd:annotation>
| <xsd:complexType>
| <xsd:choice >
| <xsd:element maxOccurs="unbounded" ref="jbsx:login-module-stack"/>
| <xsd:element maxOccurs="unbounded" ref="jbsx:auth-module"/>
| </xsd:choice>
| </xsd:complexType>
| </xsd:element>
|
The XML tested is
| <jbsx:application-policy name="conf-jaspi">
| <jbsx:authentication-jaspi>
| <jbsx:login-module-stack name="lm-stack">
| <jbsx:login-module
| code="org.jboss.security.auth.spi.UsersRolesLoginModule"
| flag="required">
| <jbsx:module-option name="usersProperties">props/jbossws-users.properties</jbsx:module-option>
| <jbsx:module-option name="rolesProperties">props/jbossws-roles.properties</jbsx:module-option>
| <jbsx:module-option name="unauthenticatedIdentity">anonymous</jbsx:module-option>
| </jbsx:login-module>
| </jbsx:login-module-stack>
| <jbsx:auth-module code="auth.module1.class.name">
| <jbsx:module-option name="usersProperties">props/jbossws-users.properties</jbsx:module-option>
| <jbsx:module-option name="rolesProperties">props/jbossws-roles.properties</jbsx:module-option>
| <jbsx:module-option name="unauthenticatedIdentity">anonymous</jbsx:module-option>
| </jbsx:auth-module>
|
| <jbsx:auth-module code="auth.module2.class.name" login-module-stack-ref="lm-stack"/>
| </jbsx:authentication-jaspi>
| </jbsx:application-policy>
|
There can be either auth-module or login-module-stack but not both.
Actually the test currently passes. Though, the SAX parser's validation is supposed to be on. I'll look into that.
Current SchemaBinding-based validation doesn't catch it. I was working on a fix for another issue and extended SchemaBinding validation to catch that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963589#3963589
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963589
19 years, 8 months
[Design of the JBoss Web Container] - no ejb link , use jndi-name in jboss-web.xml
by parveennisha
hi i am trying a delpoy a application ... it shows an error no -ejb link ??
wat should i do ..i dont find Jboss-web.xml in my application .. wat is exactly the error. should i set any class path or any refrence name ... Please help this out
THIS IS THE ERROR !!!!
Starting deployment of package:
file:/home/balamurugan/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/hris-war.war
17:46:38,762 INFO [EmbeddedCatalinaServiceSX] deploy, ctxPath=/hris-war, warUrl=file:/home/balamurugan/jboss-3.0.0_tomcat-4.0.3/server/default/tmp/deploy/server/default/deploy/hris-war.war/82.hris-war.war
17:46:38,766 ERROR [MainDeployer] could not start deployment: file:/home/balamurugan/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/hris-war.war
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: ejb-ref: ejb/HrisSessionDetailsEJB, no ejb-link match, use jndi-name in jboss-web.xml)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:309)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:678)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:513)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy4.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:405)
at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:586)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:465)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:237)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:894)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:340)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:243)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:678)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:513)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:465)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:314)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:536)
Caused by: javax.naming.NamingException: ejb-ref: ejb/HrisSessionDetailsEJB, no ejb-link match, use jndi-name in jboss-web.xml
at org.jboss.web.AbstractWebContainer.linkEjbRefs(AbstractWebContainer.java:633)
at org.jboss.web.AbstractWebContainer.parseWebAppDescriptors(AbstractWebContainer.java:458)
at org.jboss.web.AbstractWebContainer$DescriptorParser.parseWebAppDescriptors(AbstractWebContainer.java:944)
at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.initENC(EmbeddedCatalinaServiceSX.java:329)
at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(EmbeddedCatalinaServiceSX.java:316)
at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedCatalinaServiceSX.java:238)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963551#3963551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963551
19 years, 8 months