Hello Everyone,

We have a customer who is now scaling up to SSO but we are facing challenges to configure SSO with AAD.

1. Currently, Windows Authentication is working over public IP, since the server, where LFDS and STS are installed, are a member of the same domain.
2. LFDS and STS are on the same server with version 10.4.5.623.
3. All deployment is currently on On-Premise Server with Public IP on one Server where LFDS, Forms and WebClient are installed and LFDS is working with internal authentication.

• OnPremise Domain Name : customer.local
• Public IP DNS : customer.net
• User ID : customer.local\username
• Azure AD Tenant Domain is : "customer.com"

1. Below is a quick overview of the overall deployment architecture.
2. We have gone through the following

• https://support.laserfiche.com/resources/4145/configuring-laserfiche-directory-server-10-4-for-saml-authentication-with-microsoft-azure-active-directory
• https://answers.laserfiche.com/questions/103323/LFDS-to-Azure-Active-Directory#14218

We need your help to support this hybrid setup up. Is there any way that we can connect to Azure AAD, it fails at Sign-In URL which routes to the https:\\server.customer.local\LFDSSTS\saml2\sso and this hostname (server.customer.local) cannot be resolved through the internet. 

Look forward to feedback.

Rgds

Chandresh