It could an issue with the HTTP Authentication or maybe the content-type header. Could you post the curl command you used to test the authentication? It would look something like this: curl --user apiusername:apipassword --header "Content-Type: application/json" \ --noproxy "*" \ http://your_pulsesecure_appliance_hostname/api/v1/auth I added the --noproxy "*" to make sure the request doesn't go to the proxy server defined in the HTTP_PROXY environment variable.
... View more
Hello, Is it possible to rename a Role Mapping rule using the Rest API? When I attempt to rename a rule using a PUT call it returns a message saying the change was successful but it ends up creating a new rule with the new name and the old rules still exists. I could then delete the old rule with a DELETE call but I would rath just perform the rename in one call if possible. This way the rule numbers are maintained. Here's what I've tried: PUT to /api/v1/configuration/users/user-realms/realm/test_realm/role-mapping-rules/rule/OLD_RULE_NAME JSON object: Array ( [name] => New Rule Name [roles] => Array (  => testrole ) [stop-rules-processing] => true [user-name] => Array ( [test] => is [user-names] => Array (  => testuser ) ) ) Result: Array ( [result] => Array ( [info] => Array (  => Array ( [message] => Operation succeeded without warning or error! ) ) ) ) I have also tried a PUT call to: /api/v1/configuration/users/user-realms/realm/test_realm/role-mapping-rules/rule/OLD_RULE_NAME/name using this JSON object: Array ( [name] => New Rule Name ) It results in this error: Array ( [result] => Array ( [errors] => Array (  => Array ( [message] => [/configuration/users/user-realms/realm[name = "test_realm"]/role-mapping-rules/rule] Missing PolySelection ELEMENT )  => Array ( [message] => [/configuration/users/user-realms/realm[name = "test_realm"]/role-mapping-rules/rule] Merge-Create: Create instance failed. ) ) ) ) If there is a way to rename a rule in one shot please let me know. Thanks!
... View more