Can`t user unlock account (Active Directory)

122 views
Skip to first unread message

Vasilii Burca

unread,
Jan 24, 2019, 9:32:08 AM1/24/19
to RCDevs Security Solutions - Technical
Hello,

I have configured WebAdm so my user can reset their passwords and unlock their user accounts using OTP.

I am able to change a user password thru Secure Password Reset webapp using OTP to login, everything works perfect.

But I can not unlock a user account thru the same web app.

Can someone please tell me what am I doing wrong or what do I need to configure ?

Screen Shot 2019-01-24 at 16.20.52.png



[2019-01-24 16:11:45] [195.22.241.86] [PwReset:6UOB086Q] Resolved LDAP user: CN=xxxxx,CN=xxxxx,DC=xxxxxxx,DC=xxxxx (cached)
[2019-01-24 16:11:45] [195.22.241.86] [PwReset:6UOB086Q] Resolved source location: US
[2019-01-24 16:11:45] [195.22.241.86] [PwReset:6UOB086Q] Login session started for CN=xxxxx,CN=xxxxx,DC=xxxxx,DC=xxxxx
[2019-01-24 16:11:49] [195.22.241.86] [PwReset:6UOB086Q] Could not modify LDAP object 'CN=xxxxx,CN=xxxxxx,DC=xxxxx,DC=xxxxx' (Protocol error)
[2019-01-24 16:11:49] [195.22.241.86] [PwReset:6UOB086Q] Could not set user attributes for 'CN=xxxx,CN=xxxxx,DC=xxxxx,DC=xxxxx'
[2019-01-24 16:11:49] [195.22.241.86] [PwReset:6UOB086Q] Alert already sent 2019-01-24 15:58:56
[2019-01-24 16:20:43] [195.22.241.86] [PwReset:6UOB086Q] Could not modify LDAP object 'CN=xxxx,CN=xxxx,DC=xxxxx,DC=xxxxx' (Protocol error)
[2019-01-24 16:20:43] [195.22.241.86] [PwReset:6UOB086Q] Could not set user attributes for 'CN=xxxxx,CN=xxxxx,DC=xxxDC=xxx'
[2019-01-24 16:20:43] [195.22.241.86] [PwReset:6UOB086Q] Alert already sent 2019-01-24 15:58:56



SERVERS.XML


<?xml version="1.0" encoding="UTF-8" ?>

<Servers>

<!--
******************************************
***  WebADM Remote Server Connections  ***
******************************************

You can configure multiple instances for each of the following servers.
At login, WebADM will try to connect the configured servers in the same
order they appear in this file and uses the first one it successfully
establishes the connection to. If the server connection goes down, it
will automatically failover to the next configured server.

At least one LDAP server is required to run WebADM.
Supported servers: OpenLDAP, Active Directory, Novell eDirectory, 389.

Allowed LDAP parameters are:
 - name: server friendly name
 - host: server hostname or IP address
 - port: LDAP port number
   default and TLS: 389
   default SSL: 636
 - encryption: connection type
   allowed type are NONE, SSL and TLS
   default: 'NONE'
 - ca_cert: Trusted CA for SSL and TLS
 - cert_file: client certificate file
 - cert_key: client certificate key
-->

<LdapServer name="LDAP Server"
    host="xxxxxxxxxxxxx"
    port="389"
    encryption="TLS"
    ca_file="" />

<!--
<LdapServer name="LDAP Server 2"
    host="remotehost"
        port="389"
    encryption="TLS"
    ca_file="" />
-->

<!--
SQL servers are used for logs; message localizations and inventories.
Supported servers: MySQL5, MySQL8, PostgreSQL, MSSQL, Sybase, Oracle, SQLite.

Allowed LDAP parameters are:
 - type: MySQL5, MySQL8, MariaDB, PostgreSQL, MSSQL, Sybase, Oracle or SQLite.
 - name: server friendly name
 - host: server hostname or IP address
 - port: SQL port number (depends on server type)
 - user: database user
 - password: database password
 - database: database name
 - tnsname: Oracle TNS name (Oracle only)
 
With SQLite, only the 'database' must be set and other parameters are
ignored. The database is the full path to an SQLite DB file where WebADM
has full write access.

With Oracle, you can optionally use TNS names. If the 'tnsname' is set
then the 'host' and 'port' parameters are ignored and a tnsnames.ora
file must exist under the conf/ directory.
-->

<SqlServer name="SQL Server"
    type="MySQL8"
    host="127.0.0.1"
    user="xxxxxxxxm"
    password="xxxxxxxx"
    database="wxxxxxxxxxx"
        encryption="NONE" />

<!--
A session server is required for web services using sessions
such as OpenOTP. You can specify one or more SQL servers here.
The session server is included in WebADM. So you can keep the
default settings here.
-->

<SessionServer name="Session Server"
    host="localhost"
    port="4000"
        secret="" />

<!--
A PKI server (or CA) is required for signing user certificates.
The RSign PKI server is included in WebADM. So you can keep the
default settings here.
-->

<PkiServer name="PKI Server"
    host="localhost"
    port="5000"
    secret="secret"
    ca_file="" />

<!--
You need to configure RCDevs Push server(s) in order to use
TiQR Push or RCDevs Mobile Authenticator with Push login.
If you have an Enterprise license then you don't need to
register an RCDevs push account (keep user and password empty).
-->

<!--
<PushServer name="Push Server"
        host="push.rcdevs.com"
        port="7000"
    user=""
    password=""
        ca_file="" />
-->

<!--
Uncomment the following block if you have a license server
with an IP pool-based Enterprise license from RCDevs.
-->

<!--
<LicenseServer name="License Server"
        host="license.rcdevs.com"
    port="7001"
        ca_file="" />
-->

<!--
HTTP proxy servers can be used by WebADM for connecting
remote Web services and version checking.
-->

<!--
<ProxyServer name="HTTP Proxy"
    host="proxy"
        port="8080"
        user=""
        password=""
    ca_file="" />
-->

<!--
SMTP mail servers can be used by WebADM for sending emails.
If no server is specified, WebADM will use the local mailer
in /usb/sbin/sendmail to send emails.
-->


<MailServer name="SMTP Server"
        host="xxxxxxxxxx"
    port="25"
    encryption="NONE"
    ca_file="" />


</Servers>



Yoann Traut (RCDevs)

unread,
Jan 24, 2019, 12:19:18 PM1/24/19
to RCDevs Security Solutions - Technical
Hello, 

I encountered the same problem. We are troubleshooting what's going wrong. 
Thanks for the feedback. 

Regards

francois...@rcdevs.com

unread,
Feb 4, 2019, 7:33:33 AM2/4/19
to RCDevs Security Solutions - Technical
Hi 
Can you update webadm? It is solved.
Reply all
Reply to author
Forward
0 new messages