Hi Ben,

Yes, it is ready to be tested. I included a readme.txt file with all the steps 
required to deploy the additional components (The active and passive sts). 
Please, let me know if run into some issue after you start testing.

Thanks
Pablo.

-----Original Message-----
From: Ben Dewey [mailto:[email protected]] 
Sent: Thursday, October 08, 2009 6:25 PM
To: [email protected]
Subject: RE: [jira] Updated: (STONEHENGE-73) Change Stonehenge to use claims 
based security

Pablo,

Is this ready for me to download and start testing tonight?  Is there anything 
I should know before getting started?

-Ben Dewey



-----Original Message-----
From: Pablo Mariano Cibraro (JIRA) [mailto:[email protected]] 
Sent: Thursday, October 08, 2009 4:32 PM
To: [email protected]
Subject: [jira] Updated: (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
 ]

Pablo Mariano Cibraro updated STONEHENGE-73:
--------------------------------------------

    Attachment: stonehengeIdentity-08-Oct-2009.zip

This drop contains the passive and active STS implementations

> 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, stonehengeIdentity-08-Oct-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.

Reply via email to