Click HERE to see how Saviynt Intelligence is transforming the industry. |
01/15/2024 07:23 AM
I'm having some issues with update user request, when I try to update user with this method via Postman I get an error: user username is not allowed to update.
Request body:
Response:
User which I'm using for Saviynt API has all the web service right assigned on the SAV API role, I'm not sure what is causing this error:
01/15/2024 07:28 AM
User name is unique identifier and not allowed to update
01/15/2024 10:10 AM
Hi @rushikeshvartak,
According to the Saviynt API documentation (link) username is a mandatory parameter as it indicates which user is being updated:
01/15/2024 10:18 AM - edited 01/15/2024 10:18 AM
send comments parameters also
Did you configured below in global configs ?
01/15/2024 10:46 AM
Hi @rushikeshvartak,
I've added username to Mandatory Fields In Register User (not sure why it has to be defined as this setting is marked as deprecated). Also I've added a comment but the result is the same - 412 Precondition Failed:
01/15/2024 04:27 PM
Please share parameters mandatory for you - configured under global configs
01/15/2024 11:31 PM - edited 01/16/2024 04:02 AM
Hi @rushikeshvartak ,
Here is the screenshot, prior to your suggestion I didn't have any attributes selected (I've tried adding systemusername also but it didn't help):
01/16/2024 06:16 AM
Any attributes configured for create user request form
01/16/2024 06:25 AM
But create user request (createUserRequest endpoint) worked fine without adding any of these attributes, I'm having issues with updating users through updateUserRequest endpoint.
01/16/2024 06:46 AM
Hi @nmuzinic
Are you using any workflow in user modification? If not, then why are not using UpdateUser API instead? Could you please check if you can update the user with UpdateUser API (Without Workflow) ?
Regards,
Dhruv Sharma
01/16/2024 11:49 PM - edited 01/16/2024 11:49 PM
Hi @Dhruv_S,
Well that was my question also in this post, what is the difference between create/updateUser and create/updateUserRequest. We need to expose the Saviynt API to a vendor to push data into Saviynt (create and update users) and in the mentioned post create/updateUserRequest was suggested by your colleague. All we really need is to be able to do these actions in bulk using Saviynt API. Other option is SFTP integration which is mentioned in the post, but I'm not sure what happens once the file is downloaded to Saviynt and if we can do any preprocessing if needed.
To answer your question updateUser works fine, the only difference I see is that this request is not logged in the Request history but update is visible on the user Update History. Can this information be used in analytics (if needed)?
01/17/2024 08:11 PM
You can query on user update history table and fetch in analytics
01/16/2024 11:04 AM
Share attributes configured in identity config in global config
01/17/2024 12:09 AM
Hi @rushikeshvartak,
I'm not sure what you are referring to, the screenshot I've shared is from Global Config -> Identity lifecycle.
01/17/2024 08:13 PM
01/17/2024 11:40 PM
Hi,
Here is the config:
01/18/2024 07:54 PM
can you try sending all this attributes from register form in postman
01/29/2024 06:36 AM - edited 01/29/2024 06:47 AM
Hi @rushikeshvartak,
Unfortunately still the same result, even when I add all attributes that are used in the user register form still the same result for updateUserRequest endpoint (as I've mentioned previously createUserRequest works fine even with a few mandatory attributes):
@rushikeshvartak - do you have any experience with the SFTP integration, what I got from the documentation file can be downloaded to Saviynt, but I'm not sure what happens once the file is downloaded to Saviynt and if we can do any preprocessing on users if needed.
01/29/2024 12:39 PM
Try user which does not have @ in username
01/29/2024 11:22 PM
It didn't work and also users in my case have an @ character in username. If it's not supposed to be used than it shouldn't be allowed in that attribute. And if the issue is in the @character than create user request shouldn't work either. I'll raise a ticket in hope that this one will be resolved.