[
https://issues.apache.org/jira/browse/STONEHENGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Dewey closed STONEHENGE-99.
-------------------------------
Resolution: Fixed
Based on Pablo's comment this issues has been tested and is fixed.
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
