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 Ifelsethen CS <ol...@gmail.com> on 2004/11/08 02:34:49 UTC
SecurityContextToken, conversation session and uuid
Hi,
I got a question about WS-SecureConversation implementation.
Examples in section 6.2 (version 1.1, May, 2004) apparently shows
that there could be more than one SecurityContextToken in one
message or SOAP document, which implies that uuid and conversation
session are not one-to-one mapping. Or, you can say they are
one-to-one mapping but there could be more than one conversation
sessions exist in one message, simultaneously overlapping between two
communication parties. The latter seems impossible to me.
Since the current WS-SecureConversation implementation uses uuid to
identify ConversationSession, I wonder if you can give me some idea
how you think about that.
Thanks!
Oldcat
Re: SecurityContextToken, conversation session and uuid
Posted by Dimuthu Leelarathne <mu...@opensource.lk>.
Hi Ifelsethen,
Yes according to section 6.2 there could be more than one SCT. Our
implementation doesn't support this at present. However analysing the
architecture briefly, I don't see any barries to implement it. Would you
like to join us ?
Thanks for pointing that out.
Regards,
Dimuthu.
--
Lanka Software Foundation http://www.opensource.lk
> Hi,
>
> I got a question about WS-SecureConversation implementation.
> Examples in section 6.2 (version 1.1, May, 2004) apparently shows
> that there could be more than one SecurityContextToken in one
> message or SOAP document, which implies that uuid and conversation
> session are not one-to-one mapping. Or, you can say they are
> one-to-one mapping but there could be more than one conversation
> sessions exist in one message, simultaneously overlapping between two
> communication parties. The latter seems impossible to me.
>
> Since the current WS-SecureConversation implementation uses uuid to
> identify ConversationSession, I wonder if you can give me some idea
> how you think about that.
>
> Thanks!
>
> Oldcat
>
>