<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:873275559;
mso-list-type:hybrid;
mso-list-template-ids:-1046737540 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">I understand this, but this is disappointing to me for several reasons:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I want to centralize configuration so I do not have to have all client systems (our suite of hosted platforms) understand how to configure various types of authentication.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I want to centralize parsing of returned information so we do not have to have all client systems managing conversion of external data to a format useful for our applications. This is to some degree inevitable as the various applications
might have different needs, but some centralization seems useful here.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I want a common API to provide to my application programmers who in general know nothing about authentication, SAML, LDAP, etc. What you’re providing works, but does not meet this goal.<o:p></o:p></p>
<p class="MsoPlainText"><br>
Dave.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: users-bounces@shibboleth.net [mailto:users-bounces@shibboleth.net] On Behalf Of Christopher Bongaarts<br>
Sent: Tuesday, September 18, 2012 8:05 AM<br>
To: users@shibboleth.net<br>
Subject: Re: Using Shibboleth Identity Provider for Users Authenticated on an External Shibboleth System</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I think a more typical approach would be to set up your own IdP to handle the non-Shibboleth authentication sources, but have your SP use the third-party IdPs directly via a discovery mechanism of some sort.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 9/17/2012 6:39 PM, Dave Eisen wrote:<o:p></o:p></p>
<p class="MsoPlainText">> Greetings.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> I am looking to develop a centralized service to provide
<o:p></o:p></p>
<p class="MsoPlainText">> authentication services to all of my company’s hosted platforms. The
<o:p></o:p></p>
<p class="MsoPlainText">> bulk of the users will need to be authenticated against third party
<o:p></o:p></p>
<p class="MsoPlainText">> systems local to their organization. Some of the organizations use
<o:p></o:p></p>
<p class="MsoPlainText">> LDAP, some use Shibboleth, some use other protocols. We do not at this
<o:p></o:p></p>
<p class="MsoPlainText">> time need to maintain our own internal login/password files.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> We will also need data acquisition services getting additional
<o:p></o:p></p>
<p class="MsoPlainText">> information about these users such as email address, street address,
<o:p></o:p></p>
<p class="MsoPlainText">> user type, etc.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> The natural way to implement this would be for my company to host our
<o:p></o:p></p>
<p class="MsoPlainText">> own Shibboleth Identity Provider which does whatever parsing and
<o:p></o:p></p>
<p class="MsoPlainText">> configuration management needed to support this feature and then sends
<o:p></o:p></p>
<p class="MsoPlainText">> the request for the “real” authentication to the third party that
<o:p></o:p></p>
<p class="MsoPlainText">> knows the user. It is natural, but I do not know if it is technically possible.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> It is clear from the Shibboleth documentation that I can forward an
<o:p></o:p></p>
<p class="MsoPlainText">> authentication request to an LDAP system. I’m wondering how I support
<o:p></o:p></p>
<p class="MsoPlainText">> users managed by a third party Shibboleth system.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Is it possible to configure my Identity Provider to authenticate user
<o:p></o:p></p>
<p class="MsoPlainText">> foo using Shibboleth at bar.com’s Identify Provider? Different
<o:p></o:p></p>
<p class="MsoPlainText">> Identity Providers for different users? How do I do this?<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Thanks.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Dave Eisen<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Sequoia Retail Systems<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> <a href="mailto:dkeisen@sequoiars.com"><span style="color:windowtext;text-decoration:none">dkeisen@sequoiars.com</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> --<o:p></o:p></p>
<p class="MsoPlainText">> To unsubscribe from this list send an email to <o:p></o:p></p>
<p class="MsoPlainText">> <a href="mailto:users-unsubscribe@shibboleth.net"><span style="color:windowtext;text-decoration:none">users-unsubscribe@shibboleth.net</span></a><o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-- <o:p></o:p></p>
<p class="MsoPlainText">%% Christopher A. Bongaarts %% <a href="mailto:cab@umn.edu">
<span style="color:windowtext;text-decoration:none">cab@umn.edu</span></a> %%<o:p></o:p></p>
<p class="MsoPlainText">%% OIT - Identity Management %% <a href="http://umn.edu/~cab">
<span style="color:windowtext;text-decoration:none">http://umn.edu/~cab</span></a> %%<o:p></o:p></p>
<p class="MsoPlainText">%% University of Minnesota %% +1 (612) 625-1809 %%<o:p></o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
<span style="color:windowtext;text-decoration:none">users-unsubscribe@shibboleth.net</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>