<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Trying to use PowerShell / REST API to automate PAM activities in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402865#M5384</link>
    <description>&lt;P&gt;well you might need to setup an app but I haven't always found it necessary unless I want to restrict scopes, see &lt;A alt="https://docs.cyberark.com/identity-administration/latest/en/content/developer/oauth/client-cred-flow.htm?tocpath=Developer%20resources%20for%20CyberArk%20Identity%20Security%20Platform%20Shared%20Services%7CUse%20OAuth%202.0%20authorization%7C_____1" href="https://docs.cyberark.com/identity-administration/latest/en/content/developer/oauth/client-cred-flow.htm?tocpath=Developer%20resources%20for%20CyberArk%20Identity%20Security%20Platform%20Shared%20Services%7CUse%20OAuth%202.0%20authorization%7C_____1" target="_blank"&gt;Use the client credentials flow | CyberArk Docs&lt;/A&gt;. Note that following this instruction uses a slightly different endpoint /oauth2/token &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A minor point, but you don't need to convert to JSON when using Invoke-RestMethod and specifying content-type, you could just pass the $body variable and Powershell will parse it to the correct format for you. Try passing just $body and setting the content-type to xxx-www-form-urlencoded &lt;/P&gt;</description>
    <pubDate>Tue, 20 May 2025 15:12:12 GMT</pubDate>
    <dc:creator>Jon_Musker</dc:creator>
    <dc:date>2025-05-20T15:12:12Z</dc:date>
    <item>
      <title>Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402859#M5378</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ours is a Privilege Cloud environment with following format:&lt;/P&gt;&lt;P&gt;PVWA: &amp;lt;subdomain&amp;gt;.cyberark.cloud&lt;/P&gt;&lt;P&gt;Identity Admin: &amp;lt;axxxxxx&amp;gt;.my.idaptive.app&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm starting to use REST API / PowerShell scripting to automate some tasks to get details of accounts, safes, platforms etc and make necessary changes on them like editing user attributes, safes management (adding/managing members), changing platform settings (like change password version history on selected platforms etc).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a first step, I went to this URL to check the authentication process:&lt;/P&gt;&lt;P&gt;&lt;A alt="https://api-docs.cyberark.com/docs/ispss-api-auth/2c297daca8a97-api-token-authentication-for-cyber-ark-identity-security-platform-shared-services" href="https://api-docs.cyberark.com/docs/ispss-api-auth/2c297daca8a97-api-token-authentication-for-cyber-ark-identity-security-platform-shared-services" target="_blank"&gt;API token authentication for CyberArk Identity Security Platform Shared Services | Before you begin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I followed the steps in creating the service user.&lt;/P&gt;&lt;P&gt;In Step2 to get the bearer token, the Request URL for POST requires the Hostname to be in "hostname.id.cyberark.cloud" format. But my portal is not in this format. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please suggest on how to try in this type of environment where it doesn't contain any 'xxxx.id.cyberark.cloud' format. Please help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: We recently migrated from Privilege Cloud Standard tenant to ISPSS tenant, if this helps in understanding the issue better.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 00:35:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402859#M5378</guid>
      <dc:creator>swaroop_r</dc:creator>
      <dc:date>2025-05-20T00:35:19Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402860#M5379</link>
      <description>&lt;P&gt;Hi @Swaroop Rajmalgar​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you tried using Privileged Cloud Authentication REST API format and if so is it working? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/sdk/cyberark%20authentication%20-%20logon_v10.htm&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 01:41:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402860#M5379</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-05-20T01:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402861#M5380</link>
      <description>&lt;P&gt;Hi @Malhar Vora​&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, I tried that URL. The output I received is: The remote server returned an error: (403) Forbidden.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following are the details:&lt;/P&gt;&lt;CODE&gt;$pvwaURL = "https://&amp;lt;subdomain&amp;gt;.privilegecloud.cyberark.com"
$CyberArkCreds = Get-Credential
$cyberarkUsername = $CyberArkCreds.Username
$cyberarkPassword = $CyberArkCreds.GetNetworkCredential().Password
&amp;nbsp;
Write-Output "URL: $pvwaURL"
Write-Output "Username: $cyberarkUsername"
&amp;nbsp;
try {
$loginBody = @{
    username = $cyberarkUsername
    password = $cyberarkPassword
} | ConvertTo-Json
&amp;nbsp;
$sessionToken = Invoke-RestMethod -Method POST -Uri "$pvwaURL/PasswordVault/API/Auth/CyberArk/Logon" -Body $loginBody -ContentType "application/json"
&amp;nbsp;
}
catch {
Write-Output "Logout failed:"
Write-Output $_.Exception.Message
}&lt;/CODE&gt;&lt;P&gt;Output:&lt;/P&gt;&lt;P&gt;Logout failed:&lt;/P&gt;&lt;P&gt;The remote server returned an error: (403) Forbidden.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please let me know what I am missing here. &lt;/P&gt;&lt;P&gt;I tried doing research on it and asking a couple of other users, but they seem to be pointing to go with the OAUTH2 method saying ISPSS may not support CyberArk logon method coz it uses Identity user and not a local vault user (like in self-hosted / pcloud standard).  &lt;/P&gt;&lt;P&gt;Is it true that Local vault authentication is deprecated and no longer supported in ISPSS env? &lt;/P&gt;&lt;P&gt;Is OAuth2 authentication via CyberArk Identity is the only way for ISPSS env for REST API calls?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest, I'm trying to find answers for these basic questions but couldn't trust random sources.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 05:45:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402861#M5380</guid>
      <dc:creator>swaroop_r</dc:creator>
      <dc:date>2025-05-20T05:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402862#M5381</link>
      <description>&lt;P&gt;yes OAUTH is the way to go. You need to retrieve an auth token (a JWT) from CyberArk identity, that represents a user with suitable privileges in PCloud. You can then present that authorisation with every API call you make to the PCloud.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's assume your PCloud tenant subdomain is acmecorp, and that the identity tenant is abc1234.id.cyberark.cloud. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First create a user in abc1234.id.cyberark.cloud, let's say the username is svcPCloudAPI. Ensure it is a service user and add it to the appropriate roles to execute the API tasks you need.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now your API should POST to &lt;A alt="https://abc1234.id.cyberark.cloud/oauth2/platformtoken" href="https://abc1234.id.cyberark.cloud/oauth2/platformtoken" target="_blank"&gt;https://abc1234.id.cyberark.cloud/oauth2/platformtoken&lt;/A&gt; with this body&lt;/P&gt;&lt;P&gt;{ grant_type="client_credentials";client_id="svcPCloudAPI";client_secret="&amp;lt;password&amp;gt;" }&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The result from that should be a JSON document including an auth token (JWT) in the field access_token. Save this JWT in a variable (eg $auth_token = $returnvalue.access_token )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now you can start making API calls to &lt;A alt="https://acmecorp/PasswordVault/API/" href="https://acmecorp/PasswordVault/API/" target="_blank"&gt;https://acmecorp/PasswordVault/API/&lt;/A&gt; and set a header {"authorization"="Bearer &amp;lt;auth_token&amp;gt;"}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Or download the amazing @Pete Maan​&amp;nbsp;'s wonderful powershell gallery from github and re-use all that great work.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 08:36:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402862#M5381</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-05-20T08:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402863#M5382</link>
      <description>&lt;P&gt;Hi Jon,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the inputs.&lt;/P&gt;&lt;P&gt;I tried as below and receiving this error: Invoke-RestMethod : {"error":"invalid_grant","error_description":"invalid grant type "}&lt;/P&gt;&lt;P&gt;Is it due to my tenant not in the expected format of x.id.cyberark.cloud ?&lt;/P&gt;&lt;P&gt;My Identity tenant is the form of: abc1234.my.idaptive.app&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I tried below code to get the bearer token but failed. I tried several other changes too but failed:&lt;/P&gt;&lt;CODE&gt;$tenantId = "abc1234.my.idaptive.app"
$clientId = "svcuser"
$clientSecret = "password"
&amp;nbsp;
$tokenUrl = "https://$tenantId/oauth2/platformtoken"
&amp;nbsp;
$body = @{
    grant_type    = "client_credentials"
    client_id     = $clientId
    client_secret = $clientSecret
} | ConvertTo-Json
&amp;nbsp;
$response = Invoke-RestMethod -Uri $tokenUrl -Method Post -Body $body -ContentType "application/json"
&amp;nbsp;
$auth_token = $response.access_token
Write-Host "Bearer Token: $auth_token"&lt;/CODE&gt;&lt;P&gt;Output:&lt;/P&gt;&lt;CODE&gt;Invoke-RestMethod : {"error":"invalid_grant","error_description":"invalid grant type "}
At line:21 char:13
+ $response = Invoke-RestMethod -Uri $tokenUrl -Method Post -Body $body ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand
Bearer Token: &lt;/CODE&gt;&lt;P&gt;Also, do we need to have any web app created in Identity admin portal as a prerequisite for this oauth to work? Seems the self-hosted env works well, but I'm missing something from my pcloud env that is stopping me to work using ps scripts/REST API methods.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Will research further and keep trying to find something. Thank you  for your inputs Jon and Malhar &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Also will try out PSPete and see if that helps, hope it is compatible to work with my tenant format of abc1234.my.idaptive.app&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 14:53:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402863#M5382</guid>
      <dc:creator>swaroop_r</dc:creator>
      <dc:date>2025-05-20T14:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402864#M5383</link>
      <description>&lt;P&gt;Make sure your client_id is the full username, including the suffix (@cyberark.cloud.xxxxx).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You do not need to create your own OAuth2 app for this - the CyberArk OIDC Trust App in Identity is an OAuth2 server that is already configured enough for your service user to authenticate to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The "my.idaptive.app" naming convention is totally fine, if you have one of those tenants which are typically older. You can use "my.idaptive.app" any time you see a reference to "id.cyberark.cloud".&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 15:01:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402864#M5383</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-20T15:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402865#M5384</link>
      <description>&lt;P&gt;well you might need to setup an app but I haven't always found it necessary unless I want to restrict scopes, see &lt;A alt="https://docs.cyberark.com/identity-administration/latest/en/content/developer/oauth/client-cred-flow.htm?tocpath=Developer%20resources%20for%20CyberArk%20Identity%20Security%20Platform%20Shared%20Services%7CUse%20OAuth%202.0%20authorization%7C_____1" href="https://docs.cyberark.com/identity-administration/latest/en/content/developer/oauth/client-cred-flow.htm?tocpath=Developer%20resources%20for%20CyberArk%20Identity%20Security%20Platform%20Shared%20Services%7CUse%20OAuth%202.0%20authorization%7C_____1" target="_blank"&gt;Use the client credentials flow | CyberArk Docs&lt;/A&gt;. Note that following this instruction uses a slightly different endpoint /oauth2/token &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A minor point, but you don't need to convert to JSON when using Invoke-RestMethod and specifying content-type, you could just pass the $body variable and Powershell will parse it to the correct format for you. Try passing just $body and setting the content-type to xxx-www-form-urlencoded &lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 15:12:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402865#M5384</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-05-20T15:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402866#M5385</link>
      <description>&lt;P&gt;Thank you &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;@Elijah Hopkins @Jon Musker​&amp;nbsp;​&amp;nbsp;&lt;/P&gt;&lt;P&gt;I made the corrections: included full username and tried with content-type of "application/xxx-www-form-urlencoded". &lt;/P&gt;&lt;P&gt;This worked for me to get the bearer token, thanks a lot. I cleared stage 1 now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next, I'm trying to test if I'm able to access the PAM related endpoints:&lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;CODE&gt;$pvwaURL = "subdomain.privilegecloud.cyberark.com"
$platformApiUrl = "https://$pvwaURL/PasswordVault/api/Platforms"
&amp;nbsp;
$platformresponse = Invoke-RestMethod -Uri $platformApiUrl -Method Get -Headers @{
    Authorization = "Bearer $auth_token"
    Accept        = "application/json"
}
&amp;nbsp;
# Output
$platformresponse.value | ForEach-Object {
Write-Host "Platform ID: $($_.PlatformID), Name: $($_.PlatformName)"&lt;/CODE&gt;&lt;P&gt;As of now, there is no output: &lt;/P&gt;&lt;P&gt;Platform ID: , Name:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm guessing there is something to do with scope for proper access to Privilege Cloud API access or PAM API access. &lt;/P&gt;&lt;P&gt;Will try looking at the default "CyberArk OIDC Trust" App in Identity or maybe I need to create a separate OAUTH client app as described in docs. &lt;/P&gt;&lt;P&gt;Will keep you posted. Thanks a lot, the initial step was cleared to get the bearer token so will keep working on this next step now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 17:45:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402866#M5385</guid>
      <dc:creator>swaroop_r</dc:creator>
      <dc:date>2025-05-20T17:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402867#M5386</link>
      <description>&lt;P&gt;Verify that your API user is a member of the Privilege Cloud Administrators role in Identity Administration. The user may be in Identity right now, but not yet provisioned in the Privilege Cloud vault if it has not been granted a role that gives it such access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that isn't it, perhaps add some error checks to the script to see where the process is going wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For this line:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Authorization = "Bearer $auth_token"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can remove the word 'Bearer' in this approach since it should already be a part of the token you receive from Identity. I don't believe it will harm anything, though. I've seen "Bearer Bearer Bearer &amp;lt;token value&amp;gt;" work before.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 17:59:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402867#M5386</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-20T17:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402868#M5387</link>
      <description>&lt;P&gt;Sure, I already checked that this user is part of 'Privilege Cloud Administrators' role. &lt;/P&gt;&lt;P&gt;After migrating from Priv Cloud Standard to ISPSS env, the older account of 'subdomain_admin' was not having any use ISPSS. &lt;/P&gt;&lt;P&gt;So, I converted this *_admin to a OAUTH service user, and this user is already part of the Privilege Cloud Administrators role after migration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And yes, I removed the 'Bearer' word it is still working fine &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Thank you. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now trying to debug with some error checks and see where it goes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 19:07:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402868#M5387</guid>
      <dc:creator>swaroop_r</dc:creator>
      <dc:date>2025-05-20T19:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to use PowerShell / REST API to automate PAM activities</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402869#M5388</link>
      <description>&lt;P&gt;&lt;B&gt;Hey @Swaroop Rajmalgar&lt;/B&gt;​&amp;nbsp;&lt;B&gt;, just checking in — did you get an answer to your question?&lt;/B&gt;&lt;/P&gt;&lt;P&gt; If so, feel free to mark it as the best answer to help others in the community too. Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2025 07:21:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/trying-to-use-powershell-rest-api-to-automate-pam-activities/m-p/1402869#M5388</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-06-16T07:21:59Z</dc:date>
    </item>
  </channel>
</rss>

