Hi Scott, Will you add the implementation of "Act As" token into the Claims Based Security later? Do you think the current implementation of Passive STS in the patch has achieved the goal in the proposal?
On Thu, Sep 3, 2009 at 11:23 AM, Chintana Wilamuna (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750957#action_12750957] > > Chintana Wilamuna commented on STONEHENGE-73: > --------------------------------------------- > > I got over the above error. Rather than creating the Users table inside > StockTraderDB, I changed Initial Catalog=StonehengePassiveSts in User.cs > (PassiveStsDalSqlServer). > > Then I got the first error that I encountered again, > > CS1061: 'Trade.BusinessServiceClient.BSLClient' does not contain a > definition for 'getProfileIdFromStsIdentifier' and no extension method > 'getProfileIdFromStsIdentifier' accepting a first argument of type > 'Trade.BusinessServiceClient.BSLClient' could be found (are you missing a > using directive or an assembly reference?) > > In Default.aspx.cs in Trade, I changed, > > String profileId = client.getProfileIdFromStsIdentifier(identifier, uri); > > to, > > String profileId = > client.getProfileIdFromStsIdentifier(identifier.ToString(), uri); > > Then I was able to get it working. > > > Change Stonehenge to use claims based security > > ---------------------------------------------- > > > > Key: STONEHENGE-73 > > URL: https://issues.apache.org/jira/browse/STONEHENGE-73 > > Project: Stonehenge > > Issue Type: New Feature > > Components: Documentation, DOTNET_BS, DOTNET_CLIENT, DOTNET_OPS, > PHP_BS, PHP_CLIENT, PHP_OPS, WSAS_BS, WSAS_OPS > > Affects Versions: M2 > > Environment: All of the Stonehenge stock trader applications > > Reporter: Scott Golightly > > Assignee: Scott Golightly > > Attachments: Changes to Apache Stonehenge to Support Claims Based > Security.docx, Changes to Apache Stonehenge to Support Claims Based > Security.docx, Changes to Apache Stonehenge to Support Claims Based > Security.pdf, Changes to Apache Stonehenge to Support Claims Based > Security.pdf, StonehengeIdentity-02-Sep-2009.zip, > StonehengeIdentity-08-Aug-2009.zip > > > > > > I am proposing that we change the authentication and authorization > mechanism in Stonehenge to use claims based tokens rather than the current > user name/password. I am attaching a word document and a .PDF of the > document that explains in greater detail the proposal. > > -- > 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
