[JNDI/Naming/Network] - Re: java.lang.RuntimeException: mapped-name is required for
by baiyong
java.lang.RuntimeException: mapped-name is required for jdbc/GADB of deployment StockinBusinessEJB
at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:94)
at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:167)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:356)
at org.jboss.ejb3.SessionContainer.processMetadata(SessionContainer.java:140)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:292)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:356)
at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221585#4221585
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221585
17 years
[JBoss Portal] - LDAP Configuration for JBoss Portal
by NapSteros
Hi everybody,
I'm traying to configure [jboss-portal-2.7.1] to be integrated with our LDAP, but each time I deploy application under [jboss-4.2.3.GA] I receive an exception that I ignore the source.
I edit the [ldap_identity-config.xml] as follows :
| <identity-configuration>
| <datasources>
| <datasource>
| <name>LDAP</name>
| <!-- -->
| <service-name>portal:service=Module,type=LDAPConnectionContext</service-name>
| <class>org.jboss.portal.identity.ldap.LDAPConnectionContext</class>
| <!-- -->
| <config>
| <option>
| <name>ldap</name>
| <value>company.com</value>
| </option>
| <option>
| <name>port</name>
| <value>389</value>
| </option>
| <option>
| <name>adminDN</name>
| <value>company-eduid=123,ou=people,dc=company,dc=com</value>
| </option>
| <option>
| <name>adminPassword</name>
| <value>xxx</value>
| </option>
| </config>
| </datasource>
| </datasources>
| <!-- ------------------------------- -->
| <modules>
| <module>
| <type>User</type>
| <implementation>LDAP</implementation>
| <class>org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl</class>
| <config/>
| </module>
| <module>
| <type>Role</type>
| <implementation>LDAP</implementation>
| <class>org.jboss.portal.identity.ldap.LDAPExtRoleModuleImpl</class>
| <config/>
| </module>
| <module>
| <type>Membership</type>
| <implementation>LDAP</implementation>
| <config/>
| </module>
| <module>
| <type>UserProfile</type>
| <implementation>DELEGATING</implementation>
| <config>
| <option>
| <name>ldapModuleJNDIName</name>
| <value>java:/portal/LDAPUserProfileModule</value>
| </option>
| </config>
| </module>
| <module>
| <type>DBDelegateUserProfile</type>
| <implementation>DB</implementation>
| <config>
| <option>
| <name>randomSynchronizePassword</name>
| <value>true</value>
| </option>
| </config>
| </module>
| <module>
| <type>LDAPDelegateUserProfile</type>
| <implementation>LDAP</implementation>
| <config/>
| </module>
| </modules>
| <!-- ------------------------------- -->
| <options>
| <option-group>
| <group-name>common</group-name>
| <option>
| <name>userCtxDN</name>
| <value>ou=People,dc=company,dc=com</value>
| </option>
| <option>
| <name>userSearchFilter</name>
| <value><![CDATA[(&(sAMAccountName={0})(objectClass=company-person))]]></value>
| </option>
| <option>
| <name>roleCtxDN</name>
| <value>ou=Roles,dc=company,dc=com</value>
| </option>
| <option>
| <name>roleSearchFilter</name>
| <value><![CDATA[(&((sAMAccountName={0})(o=CompanyOraganisation)))]]></value>
| </option>
| </option-group>
| </options>
| <!-- ------------------------------- -->
| </identity-configuration>
|
|
and the [login-config.xml] :
| <policy>
| <!-- For the JCR CMS -->
| <application-policy name="cms">
| <authentication>
| <login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required"/>
| </authentication>
| </application-policy>
| <application-policy name="portal">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required">
| <module-option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory </module-option>
| <module-option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory </module-option>
| <module-option name="java.naming.provider.url">ldap://company.com:389/ </module-option>
| <module-option name="java.naming.security.authentication">simple</module-option>
| <module-option name="bindDN">cn=user</module-option>
| <module-option name="bindCredential">xxx</module-option>
| <module-option name="baseCtxDN">ou=People,dc=company,dc=com</module-option>
| <module-option name="baseFilter">(uid={0})</module-option>
| <module-option name="rolesCtxDN">ou=Roles,dc=company,dc=com</module-option>
| <module-option name="roleFilter">(member={1})</module-option>
| <module-option name="roleAttributeID">cn</module-option>
| <module-option name="roleRecursion">-1</module-option>
| <module-option name="searchTimeLimit">10000</module-option>
| <module-option name="searchScope">SUBTREE_SCOPE</module-option>
| <module-option name="allowEmptyPasswords">false</module-option>
| </login-module>
| <login-module code="org.jboss.portal.identity.auth.SynchronizingLoginModule" flag="optional">
| <module-option name="synchronizeIdentity">true</module-option>
| <module-option name="synchronizeRoles">true</module-option>
| <module-option name="additionalRole">Authenticated</module-option>
| <module-option name="defaultAssignedRole">User</module-option>
| <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
| <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
| <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
| <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
| </login-module>
| </authentication>
| </application-policy>
| </policy>
|
|
But unfortunately, I receive these exceptions :
| "-- JBoss AS Log--"
|
| ERROR [ModuleServicesMetaData] Default module configuration isn t complete ModuleMetaData[type=User, implementation= LDAP, serviceName=null, className=org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl config=org.jboss.portal.identity.metadata.config.ConfigMetaData@1b22cc7]
| WARN [ServiceController] Problem starting service portal:service=Module,type=IdentityServiceController
| org.jboss.portal.identity.IdentityException: Error during processing default configuration file
|
| "-- Browser error--"
|
| HTTP Status 500 -
| type Exception report
| message
| description The server encountered an internal error () that prevented it from fulfilling this request.
| exception
| javax.servlet.ServletException: org.hibernate.HibernateException: Unable to locate current JTA transaction
| org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:278)
| javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| root cause
| org.hibernate.HibernateException: Unable to locate current JTA transaction
| ...
|
I'll be so gratefull..
NapSteros,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221577#4221577
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221577
17 years
[Remoting] - make ejb3 client use ServerAuthMode=false on sslsocket to jb
by deckrider
My client works fine, but I don't want it to require the trust store. I've read how one can use SSLSocketFactory to somehow configure the client to use SSLSocketBuilder.REMOTING_SERVER_AUTH_MODE=false, but I also don't want the client to know about port 3873, only port 1099.
How would I change my stand alone test client to make this work?
I have changed jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml as follows:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="InvokerLocator">sslsocket://${jboss.bind.address}:3873</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
And I have this stand alone test client:
| import java.util.Hashtable;
| import javax.naming.InitialContext;
| import javax.naming.NamingException;
| public class TestClient {
| public static void main(String[] args) throws Exception {
| InitialContext ctx = null;
| Hashtable<String, String> props = new Hashtable<String, String>();
| props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
| props.put("java.naming.provider.url", "jnp://localhost:1099");
| props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
| try {
| ctx = new InitialContext(props);
| } catch (NamingException e) {
| e.printStackTrace();
| }
| HelloWorld hello = null;
| try {
| hello = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
| } catch (NamingException e) {
| e.printStackTrace();
| }
| System.setProperty("javax.net.ssl.trustStore", "/home/deckrider/jboss-4.2.3.GA-ssl/server/default/conf/localhost.keystore");
| System.setProperty("javax.net.ssl.trustStorePassword", "opensource");
|
| System.out.println(hello.getMessage());
| }
| }
|
|
And just for reference, here's my EJBs:
| import javax.ejb.Remote;
| import javax.ejb.Stateless;
| @Stateless
| @Remote(HelloWorld.class)
| public class HelloWorldBean implements HelloWorld {
| public String getMessage() {
| return "Hello EJB World";
| }
| }
|
| import javax.ejb.Remote;
| @Remote
| public interface HelloWorld {
| public String getMessage();
| }
|
My client works fine, but I don't want it to require the trust store. I've read how one can use SSLSocketFactory to somehow configure the client to use SSLSocketBuilder.REMOTING_SERVER_AUTH_MODE=false, but I also don't want the client to know about port 3873, only port 1099.
How would I change my stand alone test client to make this work?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221574#4221574
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221574
17 years
Mail System Error - Returned Mail
by The Post Office
The original message was received at Fri, 27 Mar 2009 20:13:59 +0600 from 129.43.68.1
----- The following addresses had permanent fatal errors -----
<jboss-user(a)lists.jboss.org>
17 years
