Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training, and more in a single search tool across platforms. Read the announcement here.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Hi,as proposed we try to replace our custom query jobs with the different methods listed. One of them is taking care of the job based on the Sav4Sav REST Connector.Setup:1. Creation of Analytics Report2. Configuration of importUserJSON3. Configuratio...
Hi, this topic is related to this closed thread: Limit One click disable user tab results The use case is the following: A certain group should be allowed to use the functionality for one click disable. To achieve this setup an advanced filter at "wh...
Hi,we want to integrate the Atlassian suite into our env. Additionally to fully replace their current used solution, we also want to create projects/spaces directly in the target system.Is this supported by Saviynt and was this already done by someon...
Hi,everytime a user is disabled via rule (Disable User), the information "Users Terminated thru rule" is added to the column comments. Is it possible to change or remove that message? Where is this fixed value stored?Thanks
Hi, I try to setup the regex to automatically generate passwords during the reset or change of password. I tried it first with the regex provided in this documentation:(?=.*\d)(?=.*[a-z])(?=.*[A-Z])(?=.*[~!@#$%^&?]).{8,12}The only adaption that I per...
Hi @rushikeshvartak ,This would result in importing the same access for all three security systems/endpoints, which is kind of a big overhead don't you think?The second critical point is, that you have multiple application shown on the request start ...
Hi @rushikeshvartak @AmitM , short update on this.The filter is working whenever you are adding "where 1=1", so the result is shown for select a from Users a where 1=1.I also asked the support why this is needed as from SQL perspective it would be th...
@naveenss This worked! Thank you so much. So for updateUserJSON you are not allowed to name the call with custom values. You need to stick to actions names.Just theoretically spoken. What would happen, if I include an unrelated third/fourth API call ...
As I still not able to get this working and don't find any helpful thread or documentation on this topic. I will provide my current try here.UpdateUserJSON:Spoiler {
"actions": {
"Update Login": {
"call": [
...