[
https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750335#action_12750335
]
Chintana Wilamuna commented on STONEHENGE-73:
---------------------------------------------
Scott,
I'm trying to get the service running and bumped into a couple of issues.
First, after giving my credentials for the sa account to connect to the
database, it complained saying that I don't have a dbo.Users table. So I got
the relevant bits from CreateStonehengePassiveSts.sql and created the Users
table in StockTraderDB.
Now, I'm getting a different error,
<error>
Compiler Error Message: 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?)
Source Error:
Line 66:
Line 67: BSLClient client = new BSLClient();
Line 68: String profileId =
client.getProfileIdFromStsIdentifier(identifier, uri);
Line 69:
Line 70:
Source File:
d:\src\stonehenge\stocktrader\dotnet\trader_client\Trade\Default.aspx.cs
Line: 68
</error>
Do I have to add the references?
> 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-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.
