timeouts in jaas.config

[IAM David Bantz]

13:22:11:543  INFO [137.229.114.251]
net.shibboleth.idp.authn.impl.ValidateUsernamePasswordAgainstJAAS:255 >
Profile Action ValidateUsernamePasswordAgainstJAAS: Login by 'dberry9' via
'ShibUserPassAuth' failedjavax.security.auth.login.LoginException:
Authentication failed:
[org.ldaptive.auth.AuthenticationResponse at 1572247851::authenticationResultCode=AUTHENTICATION_HANDLER_FAILURE,
ldapEntry=[dn=CN=dberry9,OU=userAccounts,DC=ua,DC=ad,DC=alaska,DC=edu[]],
accountState=null, result=false, resultCode=LDAP_TIMEOUT,
message=javax.naming.NamingException: LDAP response read timed out, timeout
used:3000ms., controls=null]        at
org.ldaptive.jaas.LdapLoginModule.login(LdapLoginModule.java:160)

17:46:24:316  INFO [204.90.98.254]
net.shibboleth.idp.authn.impl.ValidateUsernamePasswordAgainstJAAS:255 >
Profile Action ValidateUsernamePasswordAgainstJAAS: Login by 'mcampbell10'
via 'ShibUserPassAuth' failedjavax.security.auth.login.LoginException:
Authentication failed:
[org.ldaptive.auth.AuthenticationResponse at 1668002417::authenticationResultCode=AUTHENTICATION_HANDLER_FAILURE,
ldapEntry=[dn=CN=mcampbell10,OU=userAccounts,DC=ua,DC=ad,DC=alaska,DC=edu[]],
accountState=null, result=false, resultCode=LDAP_TIMEOUT,
message=javax.naming.NamingException: LDAP response read timed out, timeout
used:3000ms., controls=null]        at
org.ldaptive.jaas.LdapLoginModule.login(LdapLoginModule.java:160)

----

### Operating Environment Information
operating_system: Linux
operating_system_version: 3.10.0-957.12.2.el7.x86_64
operating_system_architecture: amd64
jdk_version: 1.8.0_91
available_cores: 2
used_memory: 2683 MB
maximum_memory: 3641 MB
### Identity Provider Information
idp_version: 3.4.6
start_time: 2020-10-19T13:40:22-08:00
current_time: 2020-10-22T09:36:15-08:00
uptime: 244553116 ms

On Thu, Oct 22, 2020 at 4:39 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 10/21/20, 10:25 PM, "users on behalf of IAM David Bantz" <
> users-bounces at shibboleth.net on behalf of dabantz at alaska.edu> wrote:
>
> >    I do have multiple modules (= application blocks). The connection
> timeout in the first listed URL terminates not just that
> > module but the jaas-based authentication entirely. The next in line
> module is not invoked as far as I can tell from the
> > single log message indicating failed authentication because the first
> connection attempt timed out.
>
> Barring a bug (*) that would be impossible because it's my code that runs
> them. The timeout should raise a LoginException and I catch that, and just
> run the next module.
>
> -- Scott
>
> (*) The bug would be the LDAP module raising a runtime exception and the
> logging, if any, might indicate that.
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20201022/87898829/attachment.htm>