How to change the search scope for user in the Identity Applications portal?

Gustavo Abaurre 2 months ago

Hi,

We have a situation that it is common. A user was initially a contractor and became and employee and vice-versa. Because of this, we have user with the same name as an active and also as an inactive user. On the identity Applications portal, in the Role association process, when we are selecting the user, it shows 2 users, but we cannot distinguish if it is an active or inactive user. This is because it shows first name and last name information only.

We tried to change the scope for the user lookup and user entities, one at a time, with no luck. Both users are always being presented in the user selection field. We restarted Tomcat and flush the cache, but it did not change the result.

How can we limit the scope to only active users? They are located in a separate OU then the inactive users.

Thanks.

Gustavo

Top Replies

Filip Trafisz 2 months ago +1

If there is a different value for an attribute that tells active from inactive, setting a filter in 'user' entity and/or other entities definition (the lookup one you mention) should work to hide them…

0 Geoffrey Carman 2 months ago

There is a search for Users container in ism-configuration.properties file, which is managed with configupdate.sh. If the inactive is a child container of Users, you will find it. If they are siblings you could try the parent container to both of them.

This setting is usually used for scoping UA users entirely for login (via OSP) and also for stuff like this I beleieve. There is also a similar setting for groups.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Filip Trafisz 2 months ago

If there is a different value for an attribute that tells active from inactive, setting a filter in 'user' entity and/or other entities definition (the lookup one you mention) should work to hide them. This has some drawbacks you must agree too as well, but so does the way Geoffrey described (this cuts those identities beyond access in most cases).
If you can, the best option is to leave default entity as it is and use a custom copy here.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Gustavo Abaurre 2 months ago in reply to Geoffrey Carman

I will try this one first. I don´t like to change default entities, because I´m not sure about the consequences to other processes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Gustavo Abaurre 2 months ago in reply to Filip Trafisz

Thank you Filip. I wil try Geoffrey sugestion first.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Menu

Identity Manager User Discussions

How to change the search scope for user in the Identity Applications portal?

Top Replies

Resources