Hey Troy, Thank you so much. I got this setup finally working:
- CAS 3.0.5 - Confluence 2.3.3 - Jira 3.7.1 Using Soulwing's implementation: http://www.soulwing.org/ Is that the one you are referring to in "that page has a new link to a more mature JIRA (Seraph auth API) SSO extension" ? Thanks! Kind Regards, RODRIGUEZ, Unai -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Troy Davis Sent: Sunday, May 13, 2007 6:14 AM To: Yale CAS mailing list Subject: Re: Atlassian Jira Single-Sign-On via CAS Hi Unai, I've got JIRA 3.7.x (Seraph) using CAS. It's an extension to DefaultAuthenticator that is applied per http://confluence.atlassian.com/display/DEV/Single+Sign-on+Integration+w ith+JIRA+and+Confluence I wrote this one myself, but that page has a new link to a more mature JIRA (Seraph auth API) SSO extension. Use it instead. They both extend DefaultAuthenticator. Notes: - Anonymous access: by default, JIRA will redirect to the login page rather than allow anonymous access. There is no way for a DefaultAuthenticator to tell Seraph to let the user in without authentication. Workaround: Recompile Seraph with a one-line change to SecurityFilter.java so that it doesn't redirect to the login page when JIRA's login.url is empty. - RPC: the RPC plugin (/rpc/* by default) doesn't interact with Seraph extensions. RPC still uses the JIRA internal user DB. - Users and permissions still exist in JIRA. The CAS glue handles authentication, not authorization. Hope this helps, Troy _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
