ws-wss4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex K." <alex1...@gmail.com>
Subject Re: Problem !! embbeding an IssueSecurityToken to SOAPMessage ?? SOLVED
Date Tue, 01 Nov 2005 08:23:43 GMT
Thanks Ruchith

It now works as it was supposed :0)

- Alex


On 10/30/05, Ruchith Fernando <ruchith.fernando@gmail.com> wrote:
>
> Hi Alex,
>
> I updated the serialization/deserialization of the message elements of
> the WS-Trust requests. Now when you try to get the values they should
> work properly.
>
> I noticed that u did :
> sbe.setName(SRVConstants.SRV_REQ.toString())
> to set 'RequestSecurityToken' as the element local name. This is not
> really necessary since it is added by IssueRequestSecurityToken.
>
> I'm not sure about the token type URI to be used for X509 Certs, (A
> quick glance at the WS-Trust and WS-SecurityPolicy specs wasn't much
> help :-( ) but will try to have a look at the constant value used in
> WSE 3.0 impl [1] .. have to get hold of a Windows box and get the .NET
> 2.0 and WSE 3.0 installed :-).
>
> Thanks
> Ruchith
>
>
> [1]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wseref/html/T_Microsoft_Web_Services2_Security_WSTrust_TokenTypes.asp
>
>
> On 10/26/05, Alex K. <alex1353@gmail.com> wrote:
> > Hi Ruchith,
> >
> > Unfortunately still I couldn't make any progress on this error. Have you
> > done something on it ??
> >
> > Would you please take a look at it ? I really need to get it fixed !!
> any
> > estimation on when your work may get finished ?
> >
> > Thanks for any help !
> >
> > Alex
> >
> >
> >
> >
> > On 10/21/05, Ruchith Fernando <ruchith.fernando@gmail.com> wrote:
> > > Hi Alex,
> > >
> > > Have a look this:
> > >
> >
> http://mail-archives.apache.org/mod_mbox/ws-wss4j-dev/200508.mbox/%3C559c463d050831142314dacd7e@mail.gmail.com%3E
> > >
> > > It explains the current state of the
> > > org.apache.ws.sandbox.security.trust.* stuff.
> > >
> > > maybe it'll help you get a better understanding of it :-)
> > >
> > > Thanks,
> > > Ruchith
> > >
> > > On 10/21/05, Alex K. < alex1353@gmail.com> wrote:
> > > > Thanks for ur reply.
> > > >
> > > > Yes I'm using the sanbox stuff. I try to dig dipper into this to see
> if
> > I
> > > > can fix it. I just do my best but for sure you can always do it in
> > better
> > > > way :0)
> > > >
> > > > Cheers
> > > >
> > > > Alex.
> > > >
> > > >
> > > >
> > > >
> > > > On 10/21/05, Ruchith Fernando <ruchith.fernando@gmail.com> wrote:
> > > > > Hi
> > > > >
> > > > > Very sorry about the delay in replying.
> > > > >
> > > > > I guess you are using
> > > > org.apache.ws.sandbox.security.trust.* since I
> > > > > see that the namespaces generated is according to the new WS-Trust
> > > > > spec (2005/02).
> > > > >
> > > > > If the class that u are using is
> > > > >
> > > >
> > org.apache.ws.sandbox.security.trust.message.token.RequestSecurityToken
> > > > > then, its a part of an object model that I am working on, and
> > > > > unfortunately its NOT complete and not tested as well :-(.
> Hopefully
> > > > > I'll be able to spend some time on it and get it finished. Or else
> you
> > > > > are welcome to fix anything and send a patch :-).
> > > > >
> > > > > Therefore my advice is not to use the
> > > > > org.apache.ws.sandbox.security.trust.message.token.*
> > > > stuff yet.
> > > > >
> > > > > Thanks,
> > > > > Ruchith
> > > > >
> > > > >
> > > > > On 10/21/05, Alex K. <alex1353@gmail.com> wrote:
> > > > > > I would be really appreciated for any help. I got stuck here
and
> no
> > idea
> > > > how
> > > > > > to solve it. I'm wondering why after adding the body element
> (see
> > the
> > > > below
> > > > > > code) to SOAP message "wst:RequestSecurityToken" changes to
> "/ns1"
> > ???
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Alex.
> > > > > >
> > > > > >
> > > > > > On 10/20/05, Alex K. <alex1353@gmail.com> wrote:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > 1) I'm running the below code to generate an
> > IssueRequestSeurityToken
> > > > and
> > > > > > embed
> > > > > > > it to a SOAPMessage .. By creating the securityToken I
get the
> tag
> > > > "wst:"
> > > > > > > for the TokenType and RequestType which is fine. Thought
after
> > > > generating
> > > > > > > the SOAPMessage I get "NS1:" tag for these elements which
> makes me
> > > > unable
> > > > > > to
> > > > > > > get their value later by calling getTokenType() and
> > getRequestType()
> > > > (they
> > > > > > > always return null).
> > > > > > >
> > > > > > > I have enclosed the related output as well .
> > > > > > >
> > > > > > > What am I doing wrong here ??
> > > > > > >
> > > > > > > 2) What is the constant value for X509 certificates ???
> > > > > > >
> > > > > > > Thanks for any help
> > > > > > >
> > > > > > > Alex.
> > > > > > >
> > > > > > >
> > > > > > > /*''''''''''''''''''''''''''''''''''''''''''''
> > CODE
> > > > > > ''''*/
> > > > > > >
> > > > > > >
> > > > > > > SOAPEnvelope reqSOAPMessage =new SOAPEnvelope();
> > > > > > > SOAPBodyElement sbe =null;
> > > > > > > Document requestDoc =null;
> > > > > > > WSSConfig wssconfig = WSSConfig.getDefaultWSConfig();
> > > > > > > IssueRequestSecurityToken requestToken =null;
> > > > > > > try {
> > > > > > > requestDoc =stsReqSOAPMessage.getAsDocumen
> > > > > > >
> > > > > > > t();
> > > > > > > requestToken =new
> > > > IssueRequestSecurityToken(requestDoc);
> > > > > > >
> > > > > > > // just for test
> > > > > > >
> > > > > >
> > > >
> > requestToken.setRequestType(TrustConstants.ISSUE_SECURITY_TOKEN);
> > > > > > > requestToken.setTokenType (WSConstants.X509TOKEN_NS);
> > > > > > >
> > > > > > > logger.debug(requestToken.toString ());
> > > > > > >
> > > > > > >
> > > > > > > sbe =new SOAPBodyElement( requestToken.getElement());
> > > > > > >
> > > > > > > sbe.setName (SRVConstants.SRV_REQ.toString());
> > > > > > > reqSOAPMessage.addBodyElement(sbe);
> > > > > > >
> > > > > > > logger.debug(reqSOAPMessage.toString());
> > > > > > > ...... OUT PUT
> > > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > // SecurityTokenElement
> > > > > > >
> > > > > > > <wst:RequestSecurityToken xmlns:wst="
> > > > > > > http://schemas.xmlsoap.org/ws/2005/02/trust" >
> > > > > > >
> > > > > >
> > > >
> > <wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue
> > > > > > > </wst:RequestType>
> > > > > > > <wst:TokenType>
> > > > > > >
> > > > > >
> > > >
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-=
> > > > > > > 1.0
> > > > > > > </wst:TokenType>
> > > > > > > </wst:RequestSecurityToken>
> > > > > > >
> > > > > > > //SOAPEnvelope after embbeding requestSecurityToken
> > > > > > > <soapenv:Envelope xmlns:soapenv="
> > > > > > http://schemas.xmlsoap.org/soap/envelope=
> > > > > > > /"
> > > > > > > xmlns:xsd=D"http://www.w3.org/2001/XMLSchema "
> > > > > > xmlns:xsi="
> > > > > > > http://www.w3.org/2001/XMLSchema-instance" >
> > > > > > > <soapenv:Body><ns1:RequestSecurityToken
> > xmlns:ns1="
> > > > > > > http://schemas.xmlsoap.org/ws/2005/02/trust">
> > > > > > >
> > > > > >
> > > > <ns1:RequestType>
> > http://schemas.xmlsoap.org/ws/2005/02/trust/Issue
> > > > > > > </ns1:RequestType>
> > > > > > > <ns1:TokenType>
> > > > > > >
> > > > > >
> > > >
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-=
> > > > > > > 1.0
> > > > > > > </ns1:TokenType>
> > > > > > > </ns1:RequestSecurityToken> </soapenv:Body>
> > > > > > > </soapenv:Envelope>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Ruchith
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Ruchith
> > >
> >
> >
>
>
> --
> Ruchith
>

Mime
View raw message