For kerbldap we are resolving groups also in authn stage, not only in authz stage. This was caused in 3.5 when we moved to using extensions, as before authz + authn was done in one stage in LdapAuthenticateUserCommand.java and in 3.5 it was split into two stages, but code unfortunatelly preserved.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
The result is that login time is ~two times longer.
On the other hand aaa-ldap uses connection pooling (which could improve things especially with multiple concurrent user logins) and also uses caching during nested group resolution (which means, that we won't query same group multiple times during authz phase if user is indirect member of the group and this indirect membership is reachable from several groups from direct membership). But yes, aaa-ldap is especially about adding missing functionality ...
Created attachment 1166195 [details] login log Verified with: rhevm-3.6.7.2-0.1.el6.noarch Log attached.