You are viewing a plain text version of this content. The canonical link for it is here.
Posted to stonehenge-dev@incubator.apache.org by "Ben Dewey (JIRA)" <ji...@apache.org> on 2010/03/04 02:59:27 UTC

[jira] Commented: (STONEHENGE-99) Add Support of Username Token over TLS in BSL->OPS

    [ https://issues.apache.org/jira/browse/STONEHENGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841025#action_12841025 ] 

Ben Dewey commented on STONEHENGE-99:
-------------------------------------

Pablo,

I've committed this I'm having issues building metro right now.  Please build and test on your end and resolve it it works.

> Add Support of Username Token over TLS in BSL->OPS
> --------------------------------------------------
>
>                 Key: STONEHENGE-99
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-99
>             Project: Stonehenge
>          Issue Type: New Feature
>    Affects Versions: M2
>         Environment: glassfish/metro
>            Reporter: Ming Jin
>             Fix For: M2
>
>         Attachments: Metro_OrderProcessor_UsernameTLS.patch
>
>
> As Kent suggested, we want to support more ws-security scenarios in BSL talking to OPS, one of which is Username Token over TLS. 
> This issue is about to implement Username Token over TLS in the Metro version. 
> 1. the Certificate OPS.Com is used to establish the SSL channel
> 2. the original userid and password is used to validate the user

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.