Chris, I took a circuitous route to getting Cosign to work with Angel. I used a jump page that checked to see if the user was logged in through Cosign. If they were, I called the Angel API to generate an URL that autologins them into Angel and then redirected them to that page. If they aren't logged in, then it takes them directly to Angel's home page where they can log in. I've got the same file behind a Cosign protected page that forces them to login to Cosign first and then redirects them making sure they bypass the Angel login screen; so it can be done either way.
It's not actually making Angel cosign-aware, it's just bypassing the Angel login since they already have logged into Cosign. The technique for doing this is described in Angel's programmer's reference guide. They use the REST api to get it done and it was fairly simple. I wrote my redirect page in PHP, but I think they have a Java example in the book. There are three software packages (WebCT, Angel, and Zimbra) that using autologin URLs to bypass their login without actually loading Cosign on the application. James On 4/9/2009 2:53 PM, Chris Lafty <[email protected]> wrote: > I'm looking to see if anyone will offer some pointers in cosignifying > our implementation of ANGEL. Any help will be greatly appreciated. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
