Hi Marvin, There are a few other things:
- KC's :443 service URL question (6/13/10 - I think it's a related to Uri.ToString() vs. Uri.AbsoluteUri) - Proxy ticket generation & validation testing - SAML ticket validation testing - Single Sign-Out testing - Fill in the code documentation blanks - Remove ExampleWebApp, improve ExampleWebSite - ASP.NET Web Forms subclassed controls (i.e., CasLoginStatus : LoginStatus with Single Signout support) - Additional implementations for the ticket storage (SQL Server, Oracle?) The last two could probably be deferred until a v1.1 release. If anyone can spare some time to help, please speak up. -ScottH > -----Original Message----- > From: Marvin Addison [mailto:[email protected]] > Sent: Thursday, June 17, 2010 10:49 AM > To: [email protected] > Subject: [cas-dev] .NET CAS Client Status > > The Jasig Incubating Committee is asking for an update on the .NET CAS > Client. I created some dull issues regarding documentation, > licensing, and code formatting that need to be addressed prior to a > 1.0 release. Are there any other development tasks holding up a 1.0 > release? I see several open issues in Jira, but are they blockers? > Can we target late summer at the latest? To that end I'm willing to > take point on https://issues.jasig.org/browse/NETC-18, > https://issues.jasig.org/browse/NETC-19, and documentation. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see http://www.ja- > sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
