Hi @BivonaK ,

Based on your screenshot you’re missing information that is required so IFS can authenticate to active directory.   You can click on the link below which will take you to the IFS help explaining how to t configure the Active Directory Authenticator information.  Just scroll down about halfway and you’ll see the information.

Link:  Active Directory Authenticator

You need to enter the following information.

• Hostname: Enter the fully qualified hostname of the LDAP server (for failover LDAP configuration refer to the section).
• Port: Enter the port of the LDAP server. Default values are 389 for standard connection and 636 when using SSL.
• Use SSL: This setting enables communication using TLS, turning on LDAPS instead of standard LDAP. Use of LDAPS is always recommended.
• Username: Enter the username (typically a service user account) which have read access rights in the LDAP server. It is not recommended to use an SPN if available.
• Password: Enter the password for the account specified by the username above. The first time the compatibility Active Directory Authenticator is set up, this is mandatory. If the compatibility Active Directory Authenticator is reconfigured later, it is only mandatory if a new password needs to be specified.
• User Base DN: Specify the base folder where users are located in the LDAP directory.
• Group Base DN:  Specify the root folder containing groups in the LDAP directory.

Regards,

William Klotz

Hi @BivonaK ,

If you are trying to configure the application to use AD based authentication for client logons (IEE & Aurena), the AD authenticator option that you are using is not the place to do it. The page in your screenshot is only meant to be used for backward compatibility and is only used for legacy integrations rather than client authentications.

In order to use on-premise AD based authentication you need to have ADFS v4 configured in the domain. You can use ADFS as the IDP after that.

 

For more info on this, please refer to the online tech docs using the link below

https://docs.ifs.com/techdocs/Foundation1/040_administration/210_security/015_authentication/030_configure_ADFS/default.htm

Cheers

Thank you for your answers !!

William, my screenshot was only for illustration purpose and i had filled all the field  and was available to save my configuration without error. That why i thought the problem was after this step.

Sajith, you mean that there is no way to connect to a simple AD through this way ?

As online documentation seems to say it is possible it s a bit dissapointing here. And ADFS is not a real alternative for me as now.

Thank you once again.

Hi , 

any precisions , or any opinion on this point / question ? :)

Regards

Hi @BivonaK ,

Following up on my previous comment, Yes. the only way to use AD for client authentication inApps10 would be to have ADFS in front as the authentication is open id based. ADFS is the mechanism that windows AD support openID connect. 

Cheers

Hi @BivonaK ,

Have you changed directoryId property of the user frmo UserId to AD username?

Hi All,

I was going through this kind of a setup and got below error when I try to verify AD TLS.

According to the customer, they do not see any issue from their side. Does anyone got this issue?

TIA!

Best Regards,

Rayan