User selection priority - ldap,local

[sea2space]

Hi!

I have tac_plus-ng, users and groups are taken from AD/ldap
In debug i see next:

671016: 08:57:13.373 0/00000000: - Version 138db65fa8593cdaf8efdf6012d52a26380a63cf initialized
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 authen: hdr->seq_no: 1
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 looking for user dtest realm default
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 user lookup failed
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 authen: hdr->seq_no: 3
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 looking for user dtest realm default
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 user lookup failed
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 looking for user dtest in MAVIS backend
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 result for user dtest is ACK [34 ms]
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 looking for user dtest realm default
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 user lookup succeded
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 shell login for 'dtest' from 10.250.29.138 on tty2 succeeded (profile=readwrite)

I see that first there is a search for created local users, and then in mavis backend.
Is it possible to do the opposite, so that the user search is first in mavis and then in local?

in conf file i set:

user backend = mavis
pap backend = mavis
login backend = mavis chpass

[MarcJHuber]

Hi,

no, searching for MAVIS users first is not an option. Both static and (cached) dynamic users share the same search space.

Cheers,

Marc

[sea2space]

Got it! Thanks!