Two years ago, I posted a blog entry for how to setup LDAP in V7 here.
Since then things have changed and new features were added.
But on this blog, I would like to briefly show the changes that were offered as part of U9P5 and higher.
Before we start, a suggestion would be to review the course What is new in V11 and the course titled “Update users from the LDAP directory “ offered through Sage University.
Starting with Product update 9 P5, you can set up your LDAP Sync to run automatically in such a way that a Web server user with proper group and a matching folder user with proper Functional authorization will get created for you.
In order to accomplish the above, the steps below are needed. (Please review the original blog entry, since in the scope of this entry I am not discussing the existing fields that was discussed on the previous blog post)
Conclusion: You can set up Automatic LDAP Sync such that for any new user a matching web server user and folder user will get created.
Esfahani do you know how to turn Syracuse users "inactive" when the user base account is disabled on active directory?
I was only able to achieve this by disabling the user on AD and also removing all AD groups from the users account that are used on the Syracuse Groups "Ldap goups" field....
I would like to only need to disable the user on Active directory (AD)...
"Edit your endpoint and add the Menu profile and trade profile that will be used according to each role. "
What is the purpose for filling the Menu profile? For what I have deployed I think that the trade profile will stablish the "menu profile"...
Can you clarify please?
Hello, I am not sure , I am following what your question is, If you setup LDAP, then when the users go to X3 URL, they will get prompted for a user and password which then they will enter their active directory user and password and then they can login, optionally they can choose to save the password , which then it automatically prefills next time. Regards,
Dear Sir,We are working on a project that uses SSO authentication, the user just login at windows with his credentials, and after that he enters the url ( https with port 8125 not 8124), then SSO authentication will be shown.The project uses SAGE X3U9 ERP.Is they are using different type or a third party.Why LDAP server is found at the administration , and after you define it , it will update all the users from Active Directory.Any Updates for the above? I am using X3V11.Thank you for your support.Abed Darwish
I have opened a ticket with support, thanks
Hello, For your first question, LDAP on V7 and higher are not Single sign on , so users still need to enter username and password but with the remember me setting, you can provide a similar functionality. For your second question, please provide some details on what is not working. Regards,
What version of X3 do you have? I suggest to open a case with your local support.
Dear Esfahani,Hope this email finds you well.I have created LDAP server ( Connection was successful and i get all the users from my Active Directory when i click update users .. ).The problem i faced : 1- the login in screen is yet showing username and password, it will not direct me through the page by using Single Sign On. 2- I have another server with Sage X3V11, i copied the same settings that i used in LDAP at the Sage X3V7 but it didn't work properly.Any suggestions for the above.Thank for your support.Abed Darwish
We are receiving an error when setting up the LDAP Group field under the Administration>Administration>Groups screen that says "ldap not defined". We already have the ldap server configured as you have shown in the instructions and verified a successful connection. Any ideas?
© 2016 The Sage Group plc, its licensors or its affiliated companies. Sage, Sage logos, and Sage product and service names mentioned herein are the trademarks of The Sage Group plc, its licensors, or its affiliated companies. All other trademarks are the property of their respective owners. For more information, visit www.sage.com.
Community Terms of Service | Community Guidelines | General Data Protection Regulation (GDPR) | Community Help