MS Active Directory authentication

To authenticate EVA ICS users, Microsoft Active Directory can be used.

Active Directory support is not configured by default.

System setup

Install LDAP and SASL2 development libraries

apt-get install libsasl2-dev libldap2-dev libssl-dev

Append easyad module to EVA ICS Python venv (/opt/eva/etc/venv) extras


Rebuild EVA ICS venv


EVA Controller configuration

Put the following block in controller configuration (e.g. for SFA edit /opt/eva/etc/sfa.ini)

host =
domain =
key_prefix =
ou = EVA
;ca = /path/to/ca-file.crt

Host and domain should always be specified. Default key prefix is empty, default organizational unit is EVA. CA file is not used by default.

Restart the controller

eva sfa server restart

Active Directory configuration

Log into Active Directory domain controller, open Active Directory Users and Computers and create organizational unit (default - EVA)

create AD OU

Create security groups inside organizational unit. Group name should match EVA ICS API key ID

create AD group

Assign security group to domain user. Only one OU security group should be assigned. If more security groups are assigned, EVA ICS always use the first one. If API key with such ID doesn’t exist, authentication attempt is considered as failed, despite user has more groups assigned.



After OU security group is assigned to Active Directory user, its credentials can be immediately used for authentication in EVA ICS. It’s not necessary to create user in EVA ICS controller.

If user with the same login exists in EVA ICS controller, local user has higher priority. If the provided password doesn’t match local, the local record is ignored and attempt to authenticate via Active Directory is performed.

Key prefixes

if key_prefix is specified in the controller configuration file, EVA ICS will look for API key with id {key_prefix}{AD security group}, e.g.

  • key_prefix = msad_
  • user has assigned security group EVA/operator
  • EVA ICS controller API key should have id msad_operator