Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

The new account request is not allowed because the user already has an account

Thriller
Regular Contributor
Regular Contributor

Pmanand_0-1711650406867.png

I am getting the above error when trying to request for an account in the target application which is a disconnectedapplication. The status of the account 'PRAJEN2' is 'Manually Suspended' and since we have the account name rule set for unique accounts inside the endpoint, I changed the account name using Enhanced Query Execution to include the word '-Deleted' but I am still getting the same error. What can be done to fix this? Thank you for taking a look


 

 

 

10 REPLIES 10

rushikeshvartak
All-Star
All-Star

change account status to SUSPENDED FROM IMPORT SERVICE


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

I changed the status to SUSPENDED FROM IMPORT SERVICE, but I am still getting the same error

Disable below option as shown below

rushikeshvartak_0-1711683317261.png

 


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

We have a usecase to leave this button ON. Is there a way to write a custom query at endpoint level or elsewhere that would allow creation of new accounts when they are in 'Manually Suspended' or 'Suspended from Import Service' status

Use enhanced query 

SELECT accountkey as accounts__primarykey,
CONCAT(name, ' -Deleted on ', timestamp) AS accounts__name,
'SUSPENDED FROM IMPORT SERVICE' As accounts__status
FROM
accounts
WHERE
status = 'Manually Suspended' AND
Endpointkey = '1';

change endpointkey as per need


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Thank you for your help

Please click the 'Accept As Solution' button on the reply (or replies) that best answered your original question.


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Mareetta
New Contributor III
New Contributor III

I'm facing the same issue. Status and name is updated properly from import as *deleted* and suspended from import. Also have the endpoint config "Disable New Account Request if Account Already Exists" ON. But when user goes to request again, gets error. Any suggestions?

Mareetta_0-1715144146968.png

 

 

Remove mapping from user to account from User -- Account - Remove Mapping


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Mareetta
New Contributor III
New Contributor III

without removing the user from account it should work correct?