Hi, We've finished and tested the Username token over TLS in BSL->OPS, and we're going to add it into the Metro version of Stocktrader.
In accordance with the current OPS/OPS_SEC settings in Table Services, we think it's necessary to add a new entry like "OPS_TLS" to indicate this kind of security option. How do you think? Please let us know your concerns. --Ming Jin On Mon, Sep 7, 2009 at 6:14 PM, Ming Jin (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/STONEHENGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Ming Jin updated STONEHENGE-99: > ------------------------------- > > Fix Version/s: M2 > Affects Version/s: M2 > > > 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 > > > > > > 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. > > -- Ming Jin Consultant Thoughtworks, Inc Mobile: +86 135-2125-6300 Email: [email protected] MSN: [email protected] Blog: http://blogjava.net/mingj Twitter: https://twitter.com/mingjin
