• CAS User Profile

Get Profile Pea

Generates Pool Entry Authorization (PEA) file for specified user.

Required Roles

Requires one of the following roles:

• SYSTEM_ADMIN

• NAMESPACE_ADMIN

Response Body

PEA file content

Examples

GET https://192.168.0.0:4443/object/user-cas/secret/s3/wuser1@sanity.local/pea HTTP/1.1 

Content-Type: application/xml
X-SDS-AUTH-TOKEN: <AUTH_TOKEN>

HTTP/1.1 200 OK 
Content-Type: application/xml

<pea version="1.0.0">
    <defaultkey name="wuser1@sanity.local">
        <credential id="csp1.secret" enc="base64">c2VjcmV0</credential>
    </defaultkey>
    <key type="cluster" id="19999d80-37b2-3111-9c5d-7c053bc73f1a" name="wuser1@sanity.local">
        <credential id="csp1.secret" enc="base64">c2VjcmV0</credential>
    </key>
</pea>

GET https://192.168.0.0:4443/object/user-cas/secret/s3/wuser1@sanity.local/pea.json HTTP/1.1 

Content-Type: application/json
X-SDS-AUTH-TOKEN: <AUTH_TOKEN>

HTTP/1.1 200 OK
Content-Type: application/json

{
  "pea": {
    "version": "1.0.0",
    "defaultkey": {
      "name": "wuser1@sanity.local",
      "credential": {
        "id": "csp1.secret",
        "enc": "base64",
        "content": "c2VjcmV0"
      }
    },
    "key": {
      "type": "cluster",
      "id": "19999d80-37b2-3111-9c5d-7c053bc73f1a",
      "name": "wuser1@sanity.local",
      "credential": {
        "id": "csp1.secret",
        "enc": "base64",
        "content": "c2VjcmV0"
      }
    }
  }
}

curl -H $token -H "Content-Type: application/xml" -X GET https://$nodeIp:4443/object/user-cas/secret/s3/wuser1@sanity.local/pea

HTTP/1.1 200 OK 
Content-Type: application/xml

<pea version="1.0.0">
    <defaultkey name="wuser1@sanity.local">
        <credential id="csp1.secret" enc="base64">c2VjcmV0</credential>
    </defaultkey>
    <key type="cluster" id="19999d80-37b2-3111-9c5d-7c053bc73f1a" name="wuser1@sanity.local">
        <credential id="csp1.secret" enc="base64">c2VjcmV0</credential>
    </key>
</pea>