12-16-2021 11:29 AM
We run into the issue of users, who have too many User Groups, cause the HTTP Header over load into EP3 Idp Server. They are unable to login OnBase at all.
To resolve this issue, we think about going back the AD-Enhanced without IdP. in EP3.
I wonder any one using this old approach in EP3.
Thank you.
12-16-2021 11:51 AM
Hi
Directory Service Authentication (AD - Enhanced and LDAP) are NOT supported with the Hyland IDP (OnBase Foundation and higher) as they were with the OnBase IDP (OnBase 17 and 18). In order to authenticate via AD with the Hyland IDP, you would need to federate through a third party like AD FS or Azure AD.
You can, however, run the Hyland IDP for federated authentication in the same environment as Directory Service Authentication. This way products which are pointed to the Hyland IDP use federated authentication and products which use Directory Service Authentication can use Windows Credentials for domain authentication.
Best wishes.
12-16-2021 11:51 AM
Hi
Directory Service Authentication (AD - Enhanced and LDAP) are NOT supported with the Hyland IDP (OnBase Foundation and higher) as they were with the OnBase IDP (OnBase 17 and 18). In order to authenticate via AD with the Hyland IDP, you would need to federate through a third party like AD FS or Azure AD.
You can, however, run the Hyland IDP for federated authentication in the same environment as Directory Service Authentication. This way products which are pointed to the Hyland IDP use federated authentication and products which use Directory Service Authentication can use Windows Credentials for domain authentication.
Best wishes.
12-16-2021 12:15 PM
Thank you, Adam.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.