Skip to Content.
Sympa Menu

alternative-idp - Re: [Alt IdPs] CAS Local vs. CAS Gateway Strategies

Subject: Alternative IdP Working Group

List archive

Re: [Alt IdPs] CAS Local vs. CAS Gateway Strategies


Chronological Thread 
  • From: Janemarie Duh <>
  • To: "" <>
  • Subject: Re: [Alt IdPs] CAS Local vs. CAS Gateway Strategies
  • Date: Mon, 15 Sep 2014 18:42:15 -0400

Hi, Dedra,
We'll discuss the two CAS strategies during the call on Wednesday.
So any input you have is welcome. Thank you.

Janemarie


On 09/11/2014 07:31 PM, Dedra Chamberlin wrote:
> Hi Janemarie,
>
> You just reminded me of a note I wanted to make relative to the template
> I completed for the Cirrus Bridge. That completed template was added to
> the grid in the "*Outsourced Vendor IdP" *row, which it is :-). But I
> think it could also be used to describe the use cases in these other
> rows, too, depending on a campus' current identity architecture and its
> integration needs/preferences:
>
> *Identity as-a-Service*
> *CAS Gateway*
> *Google Apps Gateway* *
> *
> *CAS (local) with Outsourced IdP*
>
> I'll be on the call next week and can further explain if necessary.
>
> - Dedra
>
>
> On Thu, Sep 11, 2014 at 4:19 PM, Janemarie Duh
> <
> <mailto:>>
> wrote:
>
> Hello,
>
> Regarding the two CAS strategies that we have on the grid, local CAS
> with an outsourced IdP and a CAS Gateway, what is the difference between
> the two rows? The only difference appears to be the protocol that is
> used between CAS and the Shibboleth/vendor IdP. Whether the solution is
> a Gateway or an IdP, they both are outsourced. What would be different
> in the CAS Gateway model? Is the protocol specifically of interest?
>
> Does it make sense to keep one or both of these on the grid? Are they a
> current possibility as opposed to something that has the potential to be
> used in the future? If these are future solutions, I think they should
> be dropped from the grid.
>
> I would still need to find volunteers for these. Bill T. said he did not
> know of any specific deployments where the IdP was operated by a third
> party. That means pinging Andrew Petro to see if he can contribute.
>
>
>
> Also, during our call on 9/17, we'll spend time summarizing and
> discussing the completed strategies. So far, they are:
>
> Cirrus Bridge (Cloud-hosted SAML IdP)
> Outsourced Shibboleth IdP
> SimpleSAML.php
>
>
> Not yet completed are:
>
> ADFS IdP
> Google Apps Gateway
> Hub and Spoke
>
>
> If anyone has any questions or concerns, please don't hesitate to let me
> know. Thanks!
>
>
> Janemarie
>
>
>
> --
> Janemarie Duh
> Identity Management Systems Architect
> Information Technology Services
> Lafayette College
>
>


--
Janemarie Duh
Identity Management Systems Architect
Information Technology Services
Lafayette College
610-330-5609
http://its.lafayette.edu




Archive powered by MHonArc 2.6.16.

Top of Page