|
Replies:
4
-
Last Post:
Mar 19, 2009 11:12 AM
by: andre0815
|
|
|
|
|
|
|
|
Re: New Features in Metro Security, Trust and SecureConversation
Posted:
Dec 23, 2008 10:22 AM
in response to: V B Kumar Jayanti
|
|
|
It would be great if you guys could get the XWSS JavaDocs on the XWSS site.
With all this new functionality, you're going to be blogging about it (I
hope to do so too), and it's helpful to the reader when you can hyperlink
particular classes you are talking about in your explanations to their
JavaDocs.
Glen
kumarjayanti wrote:
>
> Hello all,
>
> We would like to solicit your feedback/comments on the following
> proposed New Features in Metro Security, Trust and SecureConversation
> areas
>
--
View this message in context: http://www.nabble.com/New-Features-in-Metro-Security%2C-Trust-and-SecureConversation-tp21141950p21149051.html
Sent from the Metro - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net
|
|
|
|
|
|
|
|
|
Re: New Features in Metro Security, Trust and SecureConversation
Posted:
Dec 23, 2008 11:12 PM
in response to: Glen Mazza
|
|
|
|
|
Glen Mazza wrote:
>It would be great if you guys could get the XWSS JavaDocs on the XWSS site.
>With all this new functionality, you're going to be blogging about it (I
>hope to do so too), and it's helpful to the reader when you can hyperlink
>particular classes you are talking about in your explanations to their
>JavaDocs.
>
>
>
Sure we will do that. Right now the JavaDocs of XWSS which does not
include WS-Trust and WS-SecureConversation (they are independent of
XWSS though they use XWSS at the lower layers) can be obtained from the
zip <https://
file.
Thanks.
>Glen
>
>
>kumarjayanti wrote:
>
>
>>Hello all,
>>
>> We would like to solicit your feedback/comments on the following
>>proposed New Features in Metro Security, Trust and SecureConversation
>>areas
>>
>>
>>
>
>
>
[att1.html]
|
|
|
|
|
|
|
|
|
Re: New Features in Metro Security, Trust and SecureConversation
Posted:
Dec 30, 2008 2:55 AM
in response to: V B Kumar Jayanti
|
|
|
Hello Kumar!
The proposed new features seem to be great! I had to implement the Token Caching and the Renew protocol myself a few months ago.
I think that actually the STS mechanism is not very flexible. It would be great to implement some of these new features using Callbacks. For example, for the STS security mechanism:
1) The web service client try to access to a web service with a STS security mechanism.
2) If no STSCallbackHandler is defined on the client side, Metro should request the STS Token to the STS normally.
3) If a STSCallbackHandler is defined on the client side, it is called. The callback decides between requesting a new STS Token (programatically), or using a cached one.
In the same way, we could use Callbacks mechanism to implement the Renew Protocol. Although, it would be great if we could Renew and Cancel our Tokens programatically too 
Regards.
|
|
|
|
|
|
|
|
|
Re: New Features in Metro Security, Trust and SecureConversation
Posted:
Mar 19, 2009 11:12 AM
in response to: ernestojpg
|
|
|
Hello Kumar !
is a client cache option available with 1.4 ? Currently I implement caching the dispatcher and set new endpoint if a other entpoint must be called with the issued token.
caching dispatcher objects is our method on secureConversation, but in trust we must redirect endpoints. A developer friendly caching option, may setable on requestContext would be very nice !
Greats
|
|
|
|
|
java.net RSS
