IdP as a Service Working Group

[Mary McKee <>]

Hi Michael,

We attempted to get at that use case with this question:

Where would you see IdPaaS as fitting into your institution’s IAM portfolio?

• [] As a replacement for primary single sign-on (SSO) mechanism

• [] As a supplemental SSO option to allow my institution to access external (federated) resources

• [] I can’t see IdPaaS fitting into our infrastructure (please tell us why: ________)

• [] Other __________________________

E.J. and I went back and forth on wording of that second option, merging a lot of suggestions to try to keep it accessible to non-IAM audiences and focused at the strategic level (rather than the tactical/implementation level) to avoid delegation of the question to IAM staff.  

The question is admittedly leading (which was discussed on the last call, and we're open to revisiting), but we were mostly focused on making sure people considered and responded to the possibility that IdPaaS may have a place in their infrastructure even if they have existing SSO infrastructure that they're happy with.

We'd love your suggestions if you think there's a better way to get at this question, or if you think a separate question is appropriate to get at a different angle of this.

Thanks!
Mary

---

From: <> on behalf of Michael A Grady <>
Sent: Wednesday, June 19, 2019 11:02:24 AM
To:
Subject: Re: Survey progress and BaseCAMP preparations

 

So I take it the decision was to leave out anything about a "federation bridge/layer IdP as a service",  layered over Okta, Azure AD, etc. as the "identity source"?

On Jun 19, 2019, at 9:18 AM, Mary McKee <> wrote:

https://docs.google.com/document/d/1BAqgNeZY7n72ZmHw7fNkw5AyySgLLIEgQ6CgOtrlATY/edit?usp=sharing

--
Michael A. Grady
IAM Architect, Unicon, Inc.