Fisheye/Crucible 2.8.1 CAS authentication

The docs for it says "AJP authentication expects requests to be pre-authenticated via an external server before arriving at FishEye."

So if I'm fronting my Fisheye/Crucible with Apache httpd 2.2, and I use mod-auth-cas from JA-Sig, and I use the ajp connector to Fisheye/Crucible instead of http connector to Fisheye/Crucible, I can just have httpd do the authentication instead? Authorization is then controlled how?

Thank you,

1 answer

1 accepted

I just did this anyway and it seems fine. I authenticate using mod_auth_cas. I set my User's "Auth" to "AJP". I'm guessing it matches REMOTE_USER or some such variable (I don't know) but as long as the username used to authenticate against CAS is the same as a username manually configured in Fisheye/Crucible, it seems to work.


Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

286 views 38 9
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot