It looks like *handler.setAuthenticationControls(new
PasswordPolicyControl());*
*i*s now being called from pac4j-config LdaptiveAuthenticatorBuilder class:
private static SimpleBindAuthenticationHandler
getPooledBindAuthenticationHandler(final LdapAuthenticationProperties l) {
final var handler = new
SimpleBindAuthenticationHandler(newPooledConnectionFactory(l));
* handler.setAuthenticationControls(new PasswordPolicyControl());*
return handler;
}
Does not look like any option to not set the controls even via ldap.type
value.
On Tuesday, June 20, 2023 at 11:34:24 AM UTC-5 Pablo Vidaurri wrote:
> It looks like this issue has returned with version 6.6.8. I was on 6.3.7
> when I reporting the issue, it was resolved shortly after that but I never
> upgraded. Now upgrading to 6.6.8 and I see issue again.
>
> On Sunday, January 9, 2022 at 9:56:22 AM UTC-6 dfisher wrote:
>
>> On Fri, Jan 7, 2022 at 11:30 PM Pablo Vidaurri <[email protected]>
>> wrote:
>>
>>> For this method in LdapUtils, can a property be wrapped around the
>>> setAuthenticationControls
>>> call? I do not have permission to query for the OID
>>> "1.3.6.1.4.1.42.2.27.8.5.1"
>>> object that ldaptive request during user credential validation. I had to
>>> comment out that line for my deployment but I do not want to have to
>>> maintain this file.
>>>
>>>
>> I submitted a PR for this: https://github.com/apereo/cas/pull/5338
>>
>> --Daniel Fisher
>>
>>
>
--
You received this message because you are subscribed to the Google Groups "CAS
Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-dev/c58c43b6-4626-4e2a-9a59-449c1e05b39cn%40apereo.org.