Hi again!
The web service context is injected OK.
wsCtx is not null it's just the user principal object that I try to retrieve
from the wsCtx that is null. But maybe this is a result of JBWS-2074?
I've not tried it yet but I guess that
org.jboss.security.SecurityAssociation.getPrincipal().getName
Hi Richard.
I do not know if the endpoints can be shared.
They need to get different
@Resource
javax.xml.ws.WebServiceContext
references (if annotated with it).
Shared or not, the pojo endpoints need to be released sometime.
Is it a known problem that the enpoints are not released until the war
Hi again.
I noticed another thing when running this test.
In my service I have system outs in the c-tor and finalizer.
I've also added postCreate and preDestroy methods with:
| public HelloImpl(){
| System.out.println("HelloServiceImpl created!!!");
| }
|@PostConstruct
Hi!
Sorry for the the delay...
I've tried the new username token support now and it seams to work fine.
Build info:
Version: jbossws-native-3.0.6-SNAPSHOT
Build: 200901151503
Example of SOAP request:
| POST /lab_1_wsdl_first/HelloService HTTP/1.1
| SOAPAction: ""
| Content-Type: text/xml;
For anyone watching/tracking this thread:
Looks like JBWS-1999 has been implemented and is now scheduled for the 3.0.6
release.
Docs updated at:
http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options
look for POJO endpoint.
This seems to be exactly what I was looking for when I i
Ah, that looks useful.
Thanks for the update!
/Mikael
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132135#4132135
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132135
___
Ah, that looks useful.
Thanks for the update!
/Mikael
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132133#4132133
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132133
___
Hi Alessio!
Thank you for investigating this, much appreciated !
Unfortunately I do not have an EJB3 endpoint, I'm starting with a WSDL file so
I have a POJO endpoint (using wsconsume to do wsdl -2-java).
I do not think WSSE UsernameToken authentication is working for POJO endpoints
without e
Hi!
Thank you for the answer.
I have more questions though:
You are saying that:
"The Username token sent in the SOAP Message is the one used by the endpoint
server/stack to authenticate the user who is performing this request."
Good, this is what I want, I want the user to be authenticated base
One note on the server side implementation of the WS:
It is not an SLSB. I've used wsconsume and generated java files based on an
existing WSDL file.
I think that the execution ends up in the
org.jboss.ws.extensions.security.ReceiveUsernameOperation class where the
following lines are called:
s
Continuing this little discussion between me myself and I...
Found the following logs:
2008-01-15 09:19:36,480 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider]
class org.jboss.wsf.spi.invocation.SecurityAdaptorFactory Implementation:
[EMAIL PROTECTED]
2008-01-15 09:19:36,482 TRACE [org.jboss.s
So, adding:
reqContext.put(StubExt.PROPERTY_AUTH_TYPE,
StubExt.PROPERTY_AUTH_TYPE_WSSE);
|
to the client side removed the http auth header.
Guess this is because the
org.jboss.ws.core.client.RemotingConnectionImpl-createRemotingMetaData method
is called before the WSSecurityDispatcher
Hi!
I've managed to implement a web service + a client that authenticates with WSSE
UsernameToken.
My problem is that the client side is always including the HTTP Authorization
header.
Something like:
Authorization: Basic a2VybWl0OnRoZWZyb2c=
Note, the WSSE data in the SOAP header is also inclu
Hi!
I've also been trying to send messages to a remote queue. Also got stuck on the
"how do I lookup the remote queue" part...
Have seen
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureTheJMSResourceAdapterToUseARemoteConnectionFactory
but that does not explain how to get to the remote qu
Hi!
First of all, is an http session always created for each ws request?
Second, how can I disable (or reconfigure timeout of) the http session object
if it is implicitly created for each WS request?
According to http://jira.jboss.com/jira/browse/JBWS-1179 a session was always
created for each
15 matches
Mail list logo
