[
https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754194#action_12754194
]
Nicholas A Hauenstein commented on STONEHENGE-73:
-------------------------------------------------
For users that are not using the Express version of SQL Server, there is an
additional step to get this up and running.
The SqlConnection value under appSettings in
\StonehengeIdentity\identity_provider\PassiveSts\web.config needs to be updated
to point to the correct instance (i.e., remove \SQLEXPRESS)
> 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.
