Keep in mind, I'm not using an EJB endpoint. My endpoint is a POJO and it then
calls the secure session bean. Will that make a difference in your fix?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941407#3941407
Reply to the post :
http://www.jboss.com/in
No, it would not make a difference. It is the callers resposibility to provide
the correct security credentials.
Maybe your POJO endpoint is not secured, then of course there is no security
context that can automatically be propagated to the EJB layer.
View the original post :
http://www.jboss
Does anyone have any thoughts on this issue? It's a bit pressing and I would
appreciate any advice from anyone out there.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935940#3935940
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&
The best way to do this might be to use a handler:
http://labs.jboss.com/portal/jbossws/user-guide/en/html/headers-handlers.html#handlers
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936216#3936216
Reply to the post :
http://www.jboss.com/index.html?mo
http://labs.jboss.com/portal/jbossws/user-guide/en/html/secure-ejb.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936444#3936444
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936444
-
Ya, I followed all of these steps and it did not work. It was working in JBoss
4.0.3 SP1 but it no longer works in JBoss 4.0.4.CR2. I'm using EJB3, so I'm
setting up my security via annotations, but it should not matter. Here is some
code from my bean:
@Stateless
| @SecurityDomain("dbms")
Has anyone got this to work with JBoss 4.0.4.CR2? I want to be sure that this
works with the GA release so that we can go live on it. Thomas, are you still
watching this thread?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939926#3939926
Reply to the pos
Have you enabled tracing on the server side to debug this:
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityFAQ step 4.
Check the logs to see if there is any security activity on the server side.
Then follow Thomas's link from the user guide.
View the original post :
http://www.jboss.com/index
No, I have not tried adding debug tracing, but I did add a soap message hander
to the service so I could see the inbound soap message. The message no longer
contained any security information in the soap header as it previously did when
using Axis. The classes that get used on the client side
The EndpointMetaData supports
|public void setAuthMethod(String authMethod)
|{
| this.authMethod = authMethod;
|}
|
|public void setTransportGuarantee(String transportGuarantee)
|{
| this.transportGuarantee = transportGuarantee;
|}
|
whi
10 matches
Mail list logo