incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joby Abragan-Lee <Joby.Abragan-...@26ny.com>
Subject RE: [jira] Updated: (STONEHENGE-73) Change Stonehenge to use claims based security
Date Mon, 31 Aug 2009 18:33:08 GMT
Hi Scott,

I successfully went through every step in your readme file.  I thought your instructions were
very clear and easy to follow.  Thanks!

I did encounter a problem, though, when I tried to build the BusinessServiceSolution.  Here's
the error:

'Trade.IDAL.ICustomer' does not contain a definition for 'getProfileIdFromStsIdentifier' and
no extension method 'getProfileIdFromStsIdentifier' accepting a first argument of type 'Trade.IDAL.ICustomer'
could be found (are you missing a using directive or an assembly reference?)
 D:\StonehengeIdentity.Test\stocktrader\dotnet\business_service\BusinessServiceImplementation\TradeService.cs
331 36 BusinessServiceImplementation

Joby
________________________________________
From: Scott Golightly (JIRA) [jira@apache.org]
Sent: Sunday, August 30, 2009 1:35 AM
To: stonehenge-dev@incubator.apache.org
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
]

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

    Attachment: StonehengeIdentity-08-Aug-2009.zip

This is a preliminary look at the passive STS for .NET. There is a readme in the zip file
that explains how to install on a machine running the current Stonehenge code. There are still
some things that need to be cleaned up before this is ready for serious testing and a commit
but I wanted to get this out to the list. Major tasks remaining are:
1. Currently you are redirected to the login page before any other interactions. I want to
support the current functionality of a welcome page without the need for login.
2. The logout functionality doesn't work. This is related to item 1 and if you log out you
will have to close all of your browser windows before being able to log in again.
3. There are some code changes that could be done to clean up duplicate code.

I am looking for feedback on the implementation, interoperability, and the code.

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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message