Click HERE to see how Saviynt Intelligence is transforming the industry. |
03/05/2024 05:59 PM
I would like to know the criteria based on which Saviynt would detect active users who need to be inactivated if they stop coming through the authoritative source (HR source).
Will Saviynt deactivate even the built in system IDs such as admin, saviyntsupportagent* or any svc_* users set up in the product? OR
Does Saviynt rely on the user source through which the user was created before deactivating users?
If there are multiple sources of user feed based on HR transaction date, current, past or future dated hires, terminations, etc. how will this work when users are created through the future dated feed and then stop coming through the feed when the start date becomes current at which point they start to come through the current user source with updates?
03/06/2024 03:11 AM
Hi @krecpond
Below column in users table has the information where the user was imported from and used in identifying user not in file.
USERSOURCE | userSource | varchar(255) | Stores the Connection ID used in the connection through which the user is imported to EIC. Usersource represents the numerical value of the sources from which user data is imported to EIC. It is the main source from which EIC obtains the user information. |
Thanks,
Amit
If this answers your query, Please ACCEPT SOLUTION and give KUDOS.
03/06/2024 03:11 PM
Hi @Amit_Malik ,
Does this mean that in the scenario I have outlined that when a new hire stops coming through the future hire feed and starts to come through the current dated feed on the hire date, the user import job that runs against the future dated feed will deactivate this user on the user's start date?
03/07/2024 12:24 AM
Yes, it can and best it to not use "not in file" feature when you multiple sources and users can switch between sources.
Thanks,
Amit
03/06/2024 08:31 PM - edited 03/06/2024 09:50 PM
Hello @krecpond ,
Question .I would like to know the criteria based on which Saviynt would detect active users who need to be inactivated if they stop coming through the authoritative source (HR source).
Answer
For every Authrotive Source the , USER_SOUCE will be different.
Question . Will Saviynt deactivate even the built in system IDs such as admin, saviyntsupportagent* or any svc_* users set up in the product? OR Does Saviynt rely on the user source through which the user was created before?
deactivating users?
Answer.
Yes, Saviynt relies on the source to determine how a user is created. Built-in system IDs like "admin," "saviyntsupportagent*," or any "svc_*" users configured within the product will not be deactivated as the USER_SOURCE will be different.
Question. If there are multiple sources of user feed based on HR transaction date, current, past or future dated hires, terminations, etc. how will this work when users are created through the future dated feed and then stop coming through the feed when the start date becomes current at which point they start to come through the current user source with updates?
Answer. Yes, it depend on the USER_SOURCE only, For the above scenario, while imporing the users,
You can define the parameter "User Not in Feed Action" as "No Action" in userImportJob..
For Ref: https://docs.saviyntcloud.com/bundle/EIC-Admin-v24x/page/Content/Chapter10-Job-Control-Panel/Job-Cat...
Thanks