- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
09-20-2018 10:59 PM
according the doc (https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/PAS/10.4/en/Content/WebServices/Safe%20Members.htm)
i use the URL:
https://iis_ip/PasswordVault/WebServices/PIMServices.svc/Safes/sessiontest/Members
return code is 404 Not Found
09-21-2018 01:09 AM
Confirm that the account you have authenticated to the REST API with is able to see/edit members of the safe named "sessiontest".
If you log into the PVWA using the same account can you perform the task manually?
09-21-2018 01:36 AM
the 404 Not Found could also be related to the user specified under the "MemberName" property of the body of the request.
i.e. Confirm the details of the user you are trying to add as a member.
09-28-2018 08:47 AM
I agree with the other user who commented here that the request body contents should be verified to make sure that the user details are being specified correctly. However, we should also make sure that the user who generated the session token has the correct permissions on the "sessiontest" safe:
There is a flaw in the existing documentation for this method regarding the required permissions only being "Manage Safe Members" when the method actually required both "Manage Safe" and "Manage Safe Members".
09-28-2018 09:31 AM
@Stephen Palagi - always worth checking the correct rights to perform the action are held by the user performing them - but in this scenario the status code returned would be "403 Forbidden".
02-25-2020 04:12 AM
Hi community,
I've recognized a strange behaviour using REST API (CyberArk v.10.9) via psPAS modules (v.3.2.37) which refers to the original topic of the discussion.
The LDAP authentication works fine and I can also run "find-PASSafe", "Get-PASUser" and "get-PASAccount" queries successfully.
What I cannot do in REST API via psPAS modules is creating a safe, performing a "Get-PASSafe" or creating an account even though I have the respective Vault and safe permissions to do that (a manual safe creating is successful, viewing my test safe works).
The error message I am receiving is the following:
PS U:\> Get-PASSafe -SafeName SAFENAME_XXXXX -verbose
VERBOSE: GET https://URL/PasswordVault/WebServices/PIMServices.svc/Safes/SAFENAME_XXXXX with 0-byte payload
Invoke-PASRestMethod : 404 File or directory not found Server Error 404 File or directory not found The resource you are looking for might have been removed had its name changed or is temporarily unavailable
At line:104 char:13
+ ... $result = Invoke-PASRestMethod -Uri $URI -Method GET -WebSession $S ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (
404 - F...ble.
:ErrorRecord) [Invoke-PASRestMethod], Exception
+ FullyQualifiedErrorId : 404,Invoke-PASRestMethod
PS U:\> Add-PASSafe -SafeName SAFENAME_XXXXXX -Description "Any Description" -ManagingCPM PasswordManager -NumberOfVersionsRetention 3 -verbose
VERBOSE: POST https://URL/PasswordVault/WebServices/PIMServices.svc/Safes with -1-byte payload
Invoke-PASRestMethod : 404 File or directory not found Server Error 404 File or directory not found The resource you
are looking for might have been removed had its name changed or is temporarily unavailable
At line:119 char:13
+ ... $result = Invoke-PASRestMethod -Uri $URI -Method POST -Body $Body - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (
404 - F...ble.
:ErrorRecord) [Invoke-PASRestMethod], Exception
+ FullyQualifiedErrorId : 404,Invoke-PASRestMethod
Any idea on solving that topic?
@Pete Maan
@Dominik Schuh
@Martin Steinbach
Many thanks in advance!
Best regards
Mad
05-28-2020 01:51 PM
Hello @Daniel Wuerz, did you find a solution for this issue?
Thank you in advance
06-01-2023 08:43 AM
Hi everyone,
Old topic but trying my luck anyways. I have similar issue that's is quite tricky.
I'm getting server replying with (404) Not Found when I try to add through API as shared Safe member a newly created AD group that was never used before to grant permissions in pCloud.
If I add manually the same AD group on my Safe it will succeed and if I remove it then try again through API it will also succeed.
It is just the first time that will fail. I waited long enough to cater for AD replication times and discovery of new group by CyberArk, new group can be found perfectly fine when manually searched in the pCloud admin portal.
I had similar issue (bug?) trying to delegate a personal Safe to an AD user and to workaround the issue I had to programatically add the user to a pCloud role so that it is known to Identity, then the member addition to the Safe would succeed.
But I fail to see what the equivalent of above workaround might be for an AD group.
Any idea from someone ?
Thanks
Marc
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

