<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Another idea that I know of is to set the Shib SP software to only protect a single page on your system. So if you need SAML auth, direct the users there. If you need your traditional auth then send them to that location. Either way they authenticate,
you set the necessary session information that your app needs. You do have to take some extra care since none of you content will be protected by Shib itself, that will be your responsibility.</div>
<div><br>
</div>
<div>Paul</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Rob Whitener <<a href="mailto:rob.whitener@audaxhealth.com">rob.whitener@audaxhealth.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>Shibboleth Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, June 6, 2012 10:15 AM<br>
<span style="font-weight:bold">To: </span>Shibboleth Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: Dealing with different sets of users<br>
</div>
<div><br>
</div>
<div>
<div>Thank you for the responses. I figured it would be more of an app thing. I know that we are going to provide a specific url to trigger the initial auth. I was also thinking in terms of when the partner's users return to our main site, but on the backend
I think I can figure out which users belong to which group and handle it appropriately. I could see us, in the future, needing to be an identity provider so I will explore that option as well. I will check out the SPBackDoor functionality as well, that actually
sounds like exactly what I need.
<div><br>
</div>
<div>Thanks again,</div>
<div><br>
</div>
<div>Rob<br>
<div><br>
<div class="gmail_quote">On Wed, Jun 6, 2012 at 9:59 AM, Cantor, Scott <span dir="ltr">
<<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">On 6/6/12 9:47 AM, "Rob Whitener" <<a href="mailto:rob.whitener@audaxhealth.com">rob.whitener@audaxhealth.com</a>> wrote:<br>
><br>
>My company is in the process of setting up Shibboleth to integrate with a<br>
>partner who uses SAML for auth. The end goal is to have their users be<br>
>able to use our services (they are the identity provider and we are the<br>
>service provider). However, we will<br>
> still have another large set of users who authenticate directly to us<br>
>and there is no need for SAML. Is there any way in the configuration of<br>
>shibboleth to account for this or will I need to make the application<br>
>itself account for this?<br>
<br>
</div>
</div>
It isn't directly supported (it couldn't be). There are a handful of<br>
options:<br>
<br>
- stick an IdP in front of those other users to consolidate everything<br>
behind one abstraction (this is the best option, because it leads to the<br>
right UI)<br>
<br>
- do it in the application<br>
<br>
- 2.5 adds a new capability for integration with external authentication,<br>
it's in the wiki now, search for SPBackDoor<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Scott<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>