I haven't tried it. What does the official JIRA documentation say about replacing their authentication method? I know Confluence has one, which is what we followed for the documentation.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Thu, Dec 11, 2008 at 11:21 AM, Rich Renomeron - TCG < richard.renome...@tcg.com> wrote: > Has anyone successfully CASified JIRA using the JA-SIG CAS Client? > > Although there are no instructions for JIRA on the wiki, there's a > JiraCasAuthenticator classs in the Atlassian integration jar in the JA-SIG > CAS client distribution. So I followed the instructions for > Confluence<http://www.ja-sig.org/wiki/display/CASC/Configuring+Confluence+with+JASIG+CAS+Client+for+Java+3.1>, > using the "JiraCasAuthenticator" class in the seraph-config.xml file > instead. But when I attempt to access JIRA, I'm not even redirected to CAS; > instead it redirects to /jira/secure/Dashboard.jspa, which displays the > (JIRA) login page. > > Are there special wrinkles with Jira? > > Thanks, > Rich > -- > Richard J. Renomeron, Project Lead > TCG > Yes, it *can* be done! > Tel: (202) 742-8460 > Fax: (202) 986-5532 > Email: richard.renome...@tcg.com > AIM: rrenomeronTCG > www.tcg.com > > _______________________________________________ > Yale CAS mailing list > cas@tp.its.yale.edu > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list cas@tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas