[Security & JAAS/JBoss] - Flash Remoting and jaas authentication, with credential prop
by kistler59
Does anyone have any experience deploying flash remoting in jboss's tomcat environment and authenticating invocation with jaas?
We are developing an application which uses a flash ui, that communicates with our slsb deployed on jboss via the flash remoting service deployed in the tomcat environment as a servlet. We wish to be able to apply security constraints to the service which i have done by adding
anonymous wrote :
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>All resources</web-resource-name>
| Protects all resources
| <url-pattern>/*</url-pattern>
| </web-resource-collection>
| <auth-constraint>
| <role-name>FlashRole</role-name>
| </auth-constraint>
| </security-constraint>
|
| <security-role>
| <role-name>FlashRole</role-name>
| </security-role>
|
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>Test Realm</realm-name>
| </login-config>
|
to the web.xml file and setting the security domain in jboss-web.xml
When accessing the service via a web browser it prompts the user for a username and password. However we having some difficulty connecting to flashremoting.
Has anybody done this successfully or is this possible?
And will authenticating this connection with flash remoting result in the propogation of credentials from flash remoting to our slsb?
Thanks in advance.
-Keith
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962541#3962541
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962541
18 years, 5 months
[JBossWS] - Re: Connection refused
by balakrishna_narla
Hi,
i have the following problem when i try to invoke a web service deployed successfully using a web client.
21:28:31,765 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
org.jboss.ws.metadata.wsdl.WSDLException: java.io.IOException: Server returned HTTP response code: 405 for URL: http://192.168.5.128:8080/XXX/XXXX
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.getDocument(WSDLDefinitionsFactory.java:204)
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:112)
at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:273)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:110)
at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82)
at org.jboss.ws.jaxrpc.ServiceImpl.(ServiceImpl.java:96)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
at com.osit.webservice.BuilderUtil.testClient(BuilderUtil.java:21)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:88)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: Server returned HTTP response code: 405 for URL: http://192.168.5.128:8080/WInbox/WInbox
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1152)
at java.net.URL.openStream(URL.java:1007)
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.getDocument(WSDLDefinitionsFactory.java:187)
... 33 more
I've deployed the WebService developed using JWSDK into JBoss4.0.4 in the form of .WAR file which also contains the test client.
Any help regarding this will be GREATLY appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962538#3962538
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962538
18 years, 5 months
[JBoss Seam] - Re: tomcat deploy
by TLex
Yes, deploy.tomcat was the target I used.
As far I can tell, the problem is the components.xml file that is created.
Mine is:
<components>
|
| <component name="org.jboss.seam.core.init">
| <property name="myFacesLifecycleBug">false</property>
| <property name="debug">true</property>
| </component>
|
| <!-- 120 second conversation timeout -->
| <component name="org.jboss.seam.core.manager">
| <property name="conversationTimeout">120000</property>
| </component>
|
| <!-- Bootstrap Hibernate -->
| <component name="bookingDatabase"
| class="org.jboss.seam.core.ManagedHibernateSession"/>
| <component class="org.jboss.seam.core.Hibernate"/>
| <component class="org.jboss.seam.core.Microcontainer"
| installed=""/>
|
| </components>
When I remove the installed-attribute, the JNDI Service is available, but hibernate is initialised 2 times. But that's another issue.
Could you plz check if deploy.tomcat works for you and what the content of your components.xml file is.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962535#3962535
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962535
18 years, 5 months