<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
That's what I was trying to do. Our config was based off the "authenticating against multiple OUs" in the v3 docs and has worked fine. I'll read up some more and see if I can get things working.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The ldapURL stuff makes sense now. I was doing the chaining so we could use different OUs but the same ldapURL property. I was looking at it from the wrong perspective.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the info.</div>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top: 0px; margin-bottom: 0px;margin-top:0; margin-bottom:0"></p>
<div><br>
</div>
<div><br>
</div>
<div>-------------------------------</div>
<div>Craig Pluchinsky</div>
<div>IT Services</div>
<div>Indiana University of Pennsylvania</div>
<div>724-357-3327</div>
<p style="margin-top: 0px; margin-bottom: 0px;"></p>
</div>
</div>
</div>
</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of Cantor, Scott <cantor.2@osu.edu><br>
<b>Sent:</b> Monday, July 6, 2020 10:20 AM<br>
<b>To:</b> Shib Users <users@shibboleth.net><br>
<b>Subject:</b> Re: V4 LDAP Authentication</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">On 7/6/20, 10:08 AM, "users on behalf of Cantor, Scott" <users-bounces@shibboleth.net on behalf of cantor.2@osu.edu> wrote:<br>
<br>
> As far as how the code itself behaves within a single link of a chain, if it no longer handles particular settings or<br>
> approaches, that's a bug or an issue to be documented. If it supported multiple URLs in a given LdapAuthenticator<br>
> before, it should now.<br>
<br>
Except that I'm fairly certain all the advanced examples in the page are no longer complete, and that's probably what you're trying to do. All of that needs to be updated, but Daniel would have to do that.<br>
<br>
The general approach is that if you want to do very advanced things, you have to define your own bean inheriting from shibboleth.LDAPAuthenticationFactory and you need to inject the result into the LDAPCredentialValidator via p:authenticator-ref="..."<br>
<br>
The examples are probably not that far off apart from not showing that, along with not using the parent. The Aggregate DN Resolver example is building a bean called aggregateAuthenticator that is, I think, the top-level object needed to inject into the validator(s)
in the chain.<br>
<br>
-- Scott<br>
<br>
<br>
-- <br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
</div>
</span></font></div>
</div>
</body>
</html>