Shibboleth IDP 3 as CAS Server

[Jesse Martinich]

Thank you. You saved me from going down that rabbit hole.

After enabling the MemcachedStorageService, I now have attributes flowing
to the CAS client.

I am still getting "Authorization Required", but I am guessing that is a
client-side configuration issue. I will update after I have dug in some
more.

Thanks All!

Jesse


*Jesse Martinich*
Systems Administrator
Southern Oregon University | 1250 Siskiyou Blvd | Ashland OR  97520
541-552-8424


On Fri, Jun 12, 2015 at 10:04 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 6/12/15, 12:47 PM, "users on behalf of Jesse Martinich" <
> users-bounces at shibboleth.net on behalf of martinicj at sou.edu> wrote:
>
> >Please excuse my ignorance. I think Walter may have alluded to this
> yesterday... Might I need to setup back channel support for SOAP endpoints?
>
> Not if your validation call is using 443.
>
> In SAML terms, using endpoints protected by commercial certificates and
> having to implement trust on that basis is a mess. I would imagine that's
> less true of a CAS scenario where the number of such trusts is one. But I
> also think there's no reason you couldn't use a back channel port with a
> self-signed cert either, but you likely wouldn't bother unless you were
> also doing it for SAML.
>
> The IdP doesn't really pay attention to the port when it comes to the
> profile endpoints it runs, so anything on 443 is basically available on
> 8443 if it's configured to support that.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150612/1ced98b3/attachment.html>