[Security & JAAS/JBoss] - JBoss won't load login-config from webapp
by oozoo
Hi,
I got 3 projects bundled together and deployed in a single EAR. In the web-project I have a web.xml with the following content
anonymous wrote : <security-constraint>
| <web-resource-collection>
| <web-resource-name>Faces Servlet</web-resource-name>
|
| The security configuration that only allows users with
| the role SSL Explorer Gateway to access the Radis
| console web application
|
| <url-pattern>/*</url-pattern>
| <http-method>GET</http-method>
| <http-method>POST</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>1</role-name>
| <role-name>5</role-name>
| <role-name>9</role-name>
| </auth-constraint>
|
| </security-constraint>
|
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>Radis-Console</realm-name>
| </login-config>
|
| <security-role>
| Rolle normaler Benutzer
| <role-name>1</role-name>
| </security-role>
|
| <security-role>
| Rolle Stammdaten
| <role-name>5</role-name>
| </security-role>
|
| <security-role>
| Rolle Super User
| <role-name>9</role-name>
| </security-role>
I have the jboss-web.xml in the same folder
anonymous wrote : <jboss-web>
| <security-domain>java:/jaas/MyTestApp</security-domain>
| </jboss-web>
and the login-config is in the EAR project so it is deployed under /META-INF/ in the ear root directory.
anonymous wrote :
|
| <application-policy name="MyTestApp">
|
| <!-- Active directory configuration -->
| <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="roleFilter">(member={1})</module-option>
| <module-option name="roleAttributeID">memberOf</module-option>
| <module-option name="roleAttributeIsDN">true</module-option>
| <module-option name="roleNameAttributeID">cn</module-option>
| <module-option name="password-stacking">useFirstPass</module-option>
| </login-module>
| <!-- database configuration -->
| <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
| <module-option name="password-stacking">useFirstPass</module-option>
|
| (..)
|
| </login-module>
|
| </application-policy>
|
|
now it doesnt seem to load my login-config at all, it keeps trying to load the property files for the web-console application and when I remove that from the default login-config, apparently it doesnt do anything
thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164470#4164470
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164470
17 years, 12 months
[JBossWS] - SAP&wsdl from JBoss
by fil78
Hi everybody!
I have got a new task - to implement web services in SAP and in JBoss. So I am trying to implement test service - I implemented one using java and now I try to generate proxy object in SAP from wsdl. Did someone do it? and how?? - Everytime when I push generate button exception appears... Are there any traps?
Here is my wsdl:
<?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions name="MyTestService" targetNamespace="http://www.openuri.org/2008/05/HelloWorld" xmlns:tns="http://www.openuri.org/2008/05/HelloWorld" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
| <wsdl:types>
| <xs:schema targetNamespace="http://www.openuri.org/2008/05/HelloWorld" version="1.0" xmlns:tns="http://www.openuri.org/2008/05/HelloWorld" xmlns:xs="http://www.w3.org/2001/XMLSchema">
| <xs:element name="MessageDeliverException" type="tns:MessageDeliverException"/>
| <xs:element name="URISyntaxException" type="tns:URISyntaxException"/>
| <xs:complexType name="URISyntaxException">
| <xs:sequence>
| <xs:element name="index" type="xs:int"/>
| <xs:element minOccurs="0" name="input" type="xs:string"/>
| <xs:element minOccurs="0" name="message" type="xs:string"/>
| <xs:element minOccurs="0" name="reason" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="MessageDeliverException">
| <xs:sequence>
| <xs:element minOccurs="0" name="message" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </wsdl:types>
| <wsdl:message name="WSTestBean_getEmployeeName">
| <wsdl:part name="id" type="xsd:string">
| </wsdl:part>
| </wsdl:message>
| <wsdl:message name="MessageDeliverException">
| <wsdl:part name="MessageDeliverException" element="tns:MessageDeliverException">
| </wsdl:part>
| </wsdl:message>
| <wsdl:message name="WSTestBean_getEmployeeNameResponse">
| <wsdl:part name="return" type="xsd:string">
| </wsdl:part>
| </wsdl:message>
| <wsdl:message name="URISyntaxException">
| <wsdl:part name="URISyntaxException" element="tns:URISyntaxException">
| </wsdl:part>
| </wsdl:message>
| <wsdl:portType name="WSTestBean">
| <wsdl:operation name="getEmployeeName" parameterOrder="id">
| <wsdl:input message="tns:WSTestBean_getEmployeeName">
| </wsdl:input>
| <wsdl:output message="tns:WSTestBean_getEmployeeNameResponse">
| </wsdl:output>
| <wsdl:fault name="MessageDeliverException" message="tns:MessageDeliverException">
| </wsdl:fault>
| <wsdl:fault name="URISyntaxException" message="tns:URISyntaxException">
| </wsdl:fault>
| </wsdl:operation>
| </wsdl:portType>
| <wsdl:binding name="WSTestBeanBinding" type="tns:WSTestBean">
| <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
| <wsdl:operation name="getEmployeeName">
| <soap:operation soapAction=""/>
| <wsdl:input>
| <soap:body use="literal" namespace="http://www.openuri.org/2008/05/HelloWorld"/>
| </wsdl:input>
| <wsdl:output>
| <soap:body use="literal" namespace="http://www.openuri.org/2008/05/HelloWorld"/>
| </wsdl:output>
| <wsdl:fault name="MessageDeliverException">
| <soap:fault name="MessageDeliverException" use="literal"/>
| </wsdl:fault>
| <wsdl:fault name="URISyntaxException">
| <soap:fault name="URISyntaxException" use="literal"/>
| </wsdl:fault>
| </wsdl:operation>
| </wsdl:binding>
| <wsdl:service name="MyTestService">
| <wsdl:port name="WSTestBeanPort" binding="tns:WSTestBeanBinding">
| <soap:address location="http://127.0.0.1:8080/WebServiceProject/WSTestBean"/>
| </wsdl:port>
| </wsdl:service>
| </wsdl:definitions>
and here is exception:
Cannot generate proxy (object missing in WSDL, see long text)
| Message no. SPRX084
|
| Background
| During proxy generation, an interface description in WSDL format is fetched from the Integration Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
| ==> Display Query
| ==> Display WSDL Document
|
| Diagnosis
| In the WSDL document, the object
| "<message name="WSTestBean_getEmployeeName"> <pa..."
| from the namespace
| "http://www.openuri.org/2008/05/HelloWorld"
| links to the object
| ""
| from the namespace
| ""
|
| However, this last object does not exist in the WSDL document.
| ....
|
Are there any ideas about it? I will be appreciate, thanx a lot.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164467#4164467
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164467
17 years, 12 months
[Installation, Configuration & DEPLOYMENT] - Problems deploying app in a 64-bit environment
by jimmycallaghan
I've been running Jboss5.0.0.Beta4 on my local (Ubuntu) machine and have an application running nicely. Unfortunately I can't move to JBoss5.0.0.CR1 because of a problem with persistence.xml in the META-INF directory of the EAR (http://jira.jboss.org/jira/browse/JBAS-5713).
My application is deploying correctly on my local machine but I couldn't get it working on the server. Basically, JBoss seems to ignore my EJB annotations when it deploys my application and it deploys each EJB into it's default location. Thus, when another part of the application tries to do a local lookup to a bean it cannot.
Since it was OK locally I put my application, its datasources and queue definitions into the relevant directories and tested. Everything worked. I then tarred up the whole lot (JBoss, datasources, EAR etc) and put it onto the server. I untarred and started the server and the EJBs were bound into their default locations and not where my @LocalBinding and @RemoteBinding binding annotations had specified. I am using the following import statements:
import org.jboss.ejb3.annotation.LocalBinding;
| import org.jboss.ejb3.annotation.RemoteBinding;
The only thing that is different between the server and my machine is that the server is using a 64bit jdk and my PC is 32 bit. I've tried 3 different versions of Java on the server (jrockit-R27.1.0-jdk1.5.0_08, jrockit-R27.5.0-jdk1.6.0_03 and jdk1.6.0_07). I'm getting the same result each time.
Has anybody experienced anything similar?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164464#4164464
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164464
17 years, 12 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
lla(a)technodom.kz
17 years, 12 months
