mikaeljl, for the following: -
anonymous wrote : However, I've noticed that if I do:
| @Resource
| javax.xml.ws.WebServiceContext wsCtx;
| wsCtx.getUserPrincipal() will return null.
| Is this the expected result?
Can you please raise a Jira issue under JBWS and assign it to me and I
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
mikaeljl wrote :
| Afaik the postConstruct and predestroy annotations have not been supported
on a pojo webservice before, when was this support added?
|
Since JBossWS 3.0.5 release.
mikaeljl wrote :
| Anyway, I can see that the constructor and the postCreate method is called
once for
Cross reference issue JBWS-2486.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4204904#4204904
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4204904
___
jboss-user mailing list
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
mikaeljl wrote : 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 is
redeployed?
|
It's a bug.
mikaeljl wrote :
| Also note my concern about:
| @Resource
| javax.xml.ws.WebServiceContext wsCtx;
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;
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
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
Yes, that has just been implemented on trunk and we'll included in the next
release. Getting the sources from svn, giving it a try and providing feedback
now could be usefu if you have some spare time. Thanks!
View the original post :
Ah, that looks useful.
Thanks for the update!
/Mikael
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4132133#4132133
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4132133
___
Ah, that looks useful.
Thanks for the update!
/Mikael
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4132135#4132135
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4132135
___
[EMAIL PROTECTED] wrote : I did a bit of tests and investigation..
|
| [EMAIL PROTECTED] wrote : 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. This is called MessageLevel Security as defined
[EMAIL PROTECTED] wrote : mikaeljl wrote : Are there any plans for
supporting WSSE UsernameToken based authentication for POJO endpoints (without
the requirement of any additional http level authentication?
| |
| I don't have a reliable answer for this, sorry.
mikaeljl wrote : I do not think WSSE UsernameToken authentication is working
for POJO endpoints without enabling some form of http level authentication
like basic auth? Can you confirm this?
|
There's the issue of the principal you described in the previous posts. Btw
this also is related
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
I did a bit of tests and investigation..
[EMAIL PROTECTED] wrote : 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. This is called MessageLevel Security as defined by
UsernameToken profile. If you
JBoss webservices stack supports variety of endpoint deployment models:
1. Simple JDK5 POJOs that are wrapped in a war file.
2. EJB3 endpoints that are wrapped in a ejb jar file.
3. Servlet endpoints wrapped in a war file.
4. EJB2.1 endpoints using jar archive.
Now for the Servlet/POJO model
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 based
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
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:
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
22 matches
Mail list logo
