yes the time is accurate
[root@Neth248 ~]# account-provider-test dump
{
“BindDN” : “msband@domain.local”,
“LdapURI” : “ldap://dc.domain.local”,
“DiscoverDcType” : “dns”,
“StartTls” : “1”,
“port” : 389,
“host” : “dc.domain.local”,
“isAD” : “1”,
“isLdap” : “”,
“UserDN” : “DC=domain,DC=local”,
“GroupDN” : “DC=domain,DC=local”,
“BindPassword” : “**********”,
“BaseDN” : “DC=domain,DC=local”,
“LdapUriDn” : “ldap:///dc%3Ddomain%2Cdc%3Dlocal”
it work when we don’t use 2FA since I don’t need to connect to the web page with the user
here the message in /var/log/messages when I try to log with the user account
Jan 31 11:47:01 Neth248 systemd: Starting Cockpit Web Service for Users…
Jan 31 11:47:01 Neth248 remotectl: /usr/bin/chcon: can’t apply partial context to unlabeled file ‘/etc/cockpit-user/cockpit/ws-certs.d/0-self-signed.cert’
Jan 31 11:47:01 Neth248 systemd: Started Cockpit Web Service for Users.
Jan 31 11:47:01 Neth248 remotectl: remotectl: couldn’t change SELinux type context ‘etc_t’ for certificate: /etc/cockpit-user/cockpit/ws-certs.d/0-self-signed.cert: Child process exited with code 1
Jan 31 11:47:01 Neth248 cockpit-ws: Using certificate: /etc/cockpit-user/cockpit/ws-certs.d/0-self-signed.cert
Jan 31 11:47:01 Neth248 cockpit-session: pam_ssh_add: Failed adding some keys
Jan 31 11:47:01 Neth248 systemd: Created slice User Slice of me@domain.local.
Jan 31 11:47:01 Neth248 systemd: Started Session 4 of user me@domain.local.
Jan 31 11:47:01 Neth248 systemd-logind: New session 4 of user me@domain.local.
Jan 31 11:47:01 Neth248 oddjobd: Error org.freedesktop.DBus.Error.SELinuxSecurityContextUnknown: Could not determine security context for ‘:1.273’.
Jan 31 11:47:01 Neth248 cockpit-ws: cockpit-session: pam: Creating home directory for me@domain.local.
Jan 31 11:47:02 Neth248 cockpit-ws: logged in user session
Jan 31 11:47:02 Neth248 cockpit-ws: New connection to session from 127.0.0.1
Jan 31 11:47:03 Neth248 cockpit-bridge: We trust you have received the usual lecture from the local System
Jan 31 11:47:03 Neth248 cockpit-bridge: Administrator. It usually boils down to these three things:
Jan 31 11:47:03 Neth248 cockpit-bridge: #1) Respect the privacy of others.
Jan 31 11:47:03 Neth248 cockpit-bridge: #2) Think before you type.
Jan 31 11:47:03 Neth248 cockpit-bridge: #3) With great power comes great responsibility.
Jan 31 11:47:03 Neth248 cockpit-bridge: sudo: no tty present and no askpass program specified
thanks a bunch for the super fast answer