You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Malinda Kaushalye <ka...@yahoo.com> on 2004/08/13 12:10:10 UTC
WS-Trust implementation
Hi David,
Think this explanation will help you to understand the issues we are facing right now. :)
Currently the trust implementation is using the generated service only to establish a path between the client and the service.
The endpoint (i.e. the skeleton) does nothing but returns what it gets back to the client. The actual processing (issue, renew, validate) is carried out by the STSManager along with its workers (STIssuers, STValidators, STRenewers). STSManager gets the request and response SOAP envelops as DOM documents from STSServerHandler (resides in the response path of the service end) and build the response SOAP message.
(Please refer Figure: Security Token Service Architecture and Figure : Message Path at http://www.cse.mrt.ac.lk/~kaushal/securezone/archi.htm )
Now I need to find a way to plug the STSManager some where in the response path of the service�s end and "remove those erroneous and bulky generated stuff".
There are two options.
We can generate a simple service (with no errors and less number of classes) through wsdl2java and use it.
We can use your �simple security token service� and plug the STSManager.
There is one more issue.
For the moment let�s assume that the Service is working fine.
But how we can implement the client side?
Currently I�m using the generated stub and plug a STSClientHandler to the request path and use a STRequester to build the request. So that we can view the SOAP Header.
But I feel this is quite ugly.
Suppose that in secure conversation the ConversationClientHandler need to take a token from STS. So how it builds the request?
Is it a fixed STRequester(a class implementing STRequester interface), where we can specify in the client-config.wsdd (which is the method we are using right now) used by a handler (STSClientHandler)?
OR
Another custom client building the whole request (As in your case)?
So. What is your opinion on these issues?
Feel free to fire questions about the architecture. ;-)
Regards,
Malinda Kaushalye
---------------------------------
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now.