You are viewing a plain text version of this content. The canonical link for it is here.
Posted to stonehenge-dev@incubator.apache.org by "Scott Golightly (JIRA)" <ji...@apache.org> on 2009/07/02 19:33:47 UTC

[jira] Assigned: (STONEHENGE-73) Change Stonehenge to use claims based security

     [ https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Golightly reassigned STONEHENGE-73:
-----------------------------------------

    Assignee: Scott Golightly

> 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
>
>
> 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.