<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 16, 2016 at 10:33 AM, cbaker <span dir="ltr"><<a href="mailto:craigb@clemson.edu" target="_blank">craigb@clemson.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">So the ldapEntry definitely doesn't contain the grace logins.  How would I<br>
go about making a custom entry resolver, any examples or can you point me to<br>
a place in the idp source to go read even?<br></blockquote><div><br></div><div>You can probably achieve your goal just by modifying configuration.</div><div>Declare a search entry resolver bean:</div><div><br></div><div>    <!-- use the same connection pool that DN resolution uses --></div><div>    <bean id="searchEntryResolver" class="org.ldaptive.auth.SearchEntryResolver"</div><div>        p:connectionFactory-ref="bindSearchPooledConnectionFactory" /><br></div><div><br></div><div>Wire the entry resolver to your authenticator:</div><div><br></div><div><div>    <bean name="bindSearchAuthenticator" class="org.ldaptive.auth.Authenticator" p:entryResolver-ref="searchEntryResolver"</div></div><div>    ...</div><div><br></div><div>Note that entry resolution will *always* occur with this pool, regardless of whether the bind succeeded for failed.</div><div><br></div><div>--Daniel Fisher</div><div><br></div></div></div></div>