0 votes

We have a custom website for our basic people search web page to lookup users in AD as a people directory. Everything works great except for the search allows users to search AD accounts in the entire domain. Is there a way to lockdown the Search function to this peoplesearch website only to see only accounts in a separate AD Organization Unit instead of the entire domain? Right now the search in this website can find people in the entire domain instead of in the following OU: OU=User,OU=Person,DC=csu,DC=org. I know you can accomplish this task using the Home Page but we wanted to do the same in the search. Any ideas…

Thanks,

Rodney

by (80 points)

1 Answer

0 votes
by (215k points)

Update 2018

Starting with Adaxes 2018.1 it is possible to specify a top level node for Adaxes Web interface to limit the objects available in it. For details, have a look at the following tutorial: https://www.adaxes.com/tutorials_WebInterfaceCustomization_ControlObjectsDisplayedInWebInterface.htm.

Original

Hello Rodney,

Currently, the feature of limiting search in the Web Interface is not available. We have such a feature in our TODO list, it will be available in one of our future releases.

For now, you can use two workarounds for this task:

  1. Limit what users can see with the help of Security Roles

    You can use Security Roles to hide certain parts of your AD domain(s) from users. However, you should keep in mind that when using such method, you will hide the objects from users everywhere in Adaxes environment, and not only in the 'Peopele Search' Web Interface. For information on how to accomplish the task, see the following tutorial: http://www.adaxes.com/tutorials_Delegat ... mUsers.htm.

  2. Use the View Object Home Page Action as the Search function

    As you've already mentioned, you can also search for users in Adaxes Home Page Actions. For your task, you can use the View Object Home Page Action that can be used for searching for and viewing objects and that does not perform any additional actions. For information on how to set up such a task, see View Object: http://www.adaxes.com/tutorials_WebInte ... s.htm#view. To accomplish your task:

    • On the 1st step of the section, select the type of objects your users need to search for (for example, User or Contact).
    • On the 3rd step, set a specific OU or container, where the objects should be located, or specify a LDAP filter that the objects should meet to be returned by the Home Page Action.

P.S. Rodney, please check your PM inbox!

0

Adaxes Support,

I was already trying to implement option 1 before this post and I am glad the this was one of the work arounds. We will continue to use option 1 until you add this functionality into a newer release. Again thank you for your support on how to fix our issue.

Rodney

Related questions

0 votes
1 answer

The section is not defined in the available options in Adaxes and it is in the AD as well. Eg; I need to add a section called ' Security Access' and have it ... to select from options like User Directory, Internet access, Track-It account , SAP access etc.

asked Oct 13, 2021 by Aishwarya Gavali (20 points)
0 votes
1 answer

I have 18 domains managed by Adaxes and have noticed that Admin (full access) t all objects acts normally, but for piecemeal scopes like Service Desk that scopes to individual ... role (including 16 denies) and expect it to grow as we add more domains.

asked Sep 20 by DA-symplr (40 points)
0 votes
1 answer

I'm trying to schedule a report to look in a few specific OUs. Currently "Look in" location only allows for single instance or multiple drop downs. How do I schedule multiple OU locations without creating multiple reports?

asked Jul 2, 2020 by Al (20 points)
0 votes
0 answers

We are looking for a tool that can support a blacklist for password resets and that will enforce this blacklist to certain OU groups but not others, or potentially use a whitelist of users that it will not be enforced upon.

asked Mar 2, 2020 by zachThankYou (20 points)
0 votes
1 answer

We used to run AD Audit and it would provide additional details on what was locking a user's account (workstation name, application, etc...). Is there are way with Adaxes ... on what is locking an account? Or a way to pull historical data on locked accounts?

asked Nov 16, 2020 by pulsifers (20 points)
2,807 questions
2,541 answers
6,615 comments
65,161 users