This authentication setup should be done from the Management Center using Azure Active Directory Domain Services (Azure AD DS) via LDAP.
Do the following:
A user must be set up so you can query the AD.
From your IT or AD administrator, you must get the following parameters:
Below is an example of such parameters:
CN=K2vtdaadmin,cn=users,DC=k2vfabric CN=Users,DC=k2vfabric,DC=localk2-fabric-ldap.k2vfabric.localThe following steps must be carried out on all Fabric nodes by the root user:
echo "10.21.1.134 k2-fabric-ldap.k2vfabric.local" >> /etc/hosts
Connect as fabric user
Update the admin_privileges file on one fabric node only (the one that you will start with first).
In this file, we will insert the name of the group that the user will use as the fabric admin, and the AD to which the user belongs. In our example K2vtdaadmin
echo "K2vtdaadmin" > $FABRIC_HOME/config/admin_privileges
NOTE:
admin_privilegesis applied only on the very first Fabric startup. After that, role management must be done within Fabric directly (via the Management Center or Fabric commands). Modifying this file after first start has no effect.
[fabric]
SERVER_AUTHENTICATOR=adldap
[adldap_auth]
url=ldap://k2-fabric-ldap.k2vfabric.local:389
admin_dn=CN=K2vtdaadmin,cn=users,DC=k2vfabric,DC=local
admin_password=<admin-password>
users_base_dn=CN=Users,DC=k2vfabric,DC=local
You can set each parameter using merge-config.sh — an idempotent script that is safe to re-run. Use -s for the section, -k for the key, and -v for the value. For example:
$FABRIC_HOME/fabric/scripts/merge-config.sh -s fabric -k SERVER_AUTHENTICATOR -v adldap -f $FABRIC_HOME/config/config.ini
For more information about how Fabric works with LDAP, read here. For more information about SAML configuration in Fabric, please read here.
This authentication setup should be done from the Management Center using Azure Active Directory Domain Services (Azure AD DS) via LDAP.
Do the following:
A user must be set up so you can query the AD.
From your IT or AD administrator, you must get the following parameters:
Below is an example of such parameters:
CN=K2vtdaadmin,cn=users,DC=k2vfabric CN=Users,DC=k2vfabric,DC=localk2-fabric-ldap.k2vfabric.localThe following steps must be carried out on all Fabric nodes by the root user:
echo "10.21.1.134 k2-fabric-ldap.k2vfabric.local" >> /etc/hosts
Connect as fabric user
Update the admin_privileges file on one fabric node only (the one that you will start with first).
In this file, we will insert the name of the group that the user will use as the fabric admin, and the AD to which the user belongs. In our example K2vtdaadmin
echo "K2vtdaadmin" > $FABRIC_HOME/config/admin_privileges
NOTE:
admin_privilegesis applied only on the very first Fabric startup. After that, role management must be done within Fabric directly (via the Management Center or Fabric commands). Modifying this file after first start has no effect.
[fabric]
SERVER_AUTHENTICATOR=adldap
[adldap_auth]
url=ldap://k2-fabric-ldap.k2vfabric.local:389
admin_dn=CN=K2vtdaadmin,cn=users,DC=k2vfabric,DC=local
admin_password=<admin-password>
users_base_dn=CN=Users,DC=k2vfabric,DC=local
You can set each parameter using merge-config.sh — an idempotent script that is safe to re-run. Use -s for the section, -k for the key, and -v for the value. For example:
$FABRIC_HOME/fabric/scripts/merge-config.sh -s fabric -k SERVER_AUTHENTICATOR -v adldap -f $FABRIC_HOME/config/config.ini
For more information about how Fabric works with LDAP, read here. For more information about SAML configuration in Fabric, please read here.