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

Scott Golightly updated STONEHENGE-73:
--------------------------------------

    Attachment: Changes to Apache Stonehenge to Support Claims Based 
Security.pdf
                Changes to Apache Stonehenge to Support Claims Based 
Security.docx

The Word document and the .PDF are the same. I included the .PDF for broad 
reach. The document details the proposal to modify the Stonehenge stocktrader 
application to use claims based security.

> 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
>         Attachments: Changes to Apache Stonehenge to Support Claims Based 
> Security.docx, 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.

Reply via email to