Access Manager v3 API for PubNub Ruby SDK

Access Manager allows you to enforce security controls for client access to resources within the PubNub Platform. With Access Manager v3, your servers can grant their clients tokens with embedded permissions that provide access to individual PubNub resources:

For a limited period of time.
Through resource lists or patterns (regular expressions).
In a single API request, even if permission levels differ (read to space-1 and write to space-2).

You can add the authorizedUserId parameter to the grant request to restrict the token usage to one client with a given userId. Once specified, only this authorizedUserId will be able to use the token to make API requests for the specified resources, according to permissions given in the grant request.

For more information about Access Manager v3, refer to Manage Permissions with Access Manager v3.

Grant Token

Requires Access Manager add-onRequires that the Access Manager add-on is enabled for your key. See this page on enabling add-on features on your keys:
https://support.pubnub.com/hc/en-us/articles/360051974791-How-do-I-enable-add-on-features-for-my-keys-

The grantToken() method generates a time-limited authorization token with an embedded access control list. The token defines time to live (ttl), authorizedUserId, and a set of permissions giving access to one or more resources:

spaces
users (other users' metadata, such as their names or avatars)

Only this authorizedUserId will be able to use the token with the defined permissions. The authorized client will send the token to PubNub with each request until the token's ttl expires. Any unauthorized request or a request made with an invalid token will return a 403 with a respective error message.

Permissions

The grant request allows your server to securely grant your clients access to the resources within the PubNub Platform. There is a limited set of operations the clients can perform on every resource:

Resource	Permissions
`space`	`read`, `write`, `get`, `manage`, `update`, `join`, `delete`
`user`	`get`, `update`, `delete`

For permissions and API operations mapping, refer to Manage Permissions with Access Manager v3.

TTL

The ttl (time to live) parameter is the number of minutes before the granted permissions expire. The client will require a new token to be granted before expiration to ensure continued access. ttl is a required parameter for every grant call and there is no default value set for it. The max value for ttl is 43,200 (30 days).

Recommended `ttl` value

For security reasons, it's recommended to set ttl between 10 and 60, and create a new token before this ttl elapses.

For more details, see TTL in Access Manager v3.

RegEx

If you prefer to specify permissions by setting patterns, rather than listing all resources one by one, you can use regular expressions. To do this, set RegEx permissions as patterns before making a grant request.

For more details, see RegEx in Access Manager v3.

Authorized User ID

Setting an authorizedUserId in the token helps you specify which client device should use this token in every request to PubNub. This will ensure that all requests to PubNub are authorized before PubNub processes them. If authorizedUserId isn't specified during the grant request, the token can be used by any client with any userId. It's recommended to restrict tokens to a single authorizedUserId to prevent impersonation.

For more details, see Authorized UUID in Access Manager v3.

Method(s)

grant_token(ttl: ttl, authorized_user_id: authorized_user_id, users_permissions: users, spaces_permissions: spaces)

Parameter	Type	Required	Default	Description
`ttl`	`Integer`	Yes	n/a	Total number of minutes for which the token is valid. The minimum allowed value is `1`. The maximum is `43,200` minutes (30 days).
`authorized_user_id`	`String`	Optional	n/a	Single `uuid` which is authorized to use the token to make API requests to PubNub.
`users_permissions`	`Hash`	Optional	n/a	Hash containing all User permissions provided as a list of individual permissions or RegEx patterns, for example: `{"user-1": Pubnub::Permissions.res(get: true, update: true, delete: true),"^user-2.$": Pubnub::Permissions.pat(...)}`.
`spaces_permissions`	`Hash`	Optional	n/a	Hash containing all Space permissions provided as a list of individual permissions or RegEx patterns, for example: `{"space-1": Pubnub::Permissions.res(read: true, write: true, manage: true, delete: true, get: true, update: true, join: true),"^space-2.$": Pubnub::Permissions.pat(...)}`.
`meta`	`Object`	Optional	n/a	Extra metadata to be published with the request. Values must be scalar only; arrays or objects aren't supported.

Required key/value mappings

For a successful request, you must specify permissions for at least one User or Space, either as a resource list or as a pattern (RegEx).

Basic Usage

pubnub.grant_token(
    ttl: 15,
    authorized_user_id: "my-authorized-userId",
    spaces_permissions: {
      "my-space": Pubnub::Permissions.res(
        read: true
      )    
    }
);

Returns

#<Pubnub::Envelope
    @result = {
        :data => {
            "message" => "Success",
            "token" => "p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI"
        }
    },
    @status = {
        :code => 200
    }
>

Other Examples

Grant an authorized client different levels of access to various resources in a single call:

The code below grants my-authorized-userId:

Read access to space-a, and get to userId-c.
Read/write access to space-b, space-c, space-d, and get/update to userId-d.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-userId",
      spaces_permissions: {
            "space-a": Pubnub::Permission.res(
               read: true
            ),
            "space-b": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "space-c": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "space-d": Pubnub::Permission.res(
               read: true,
               write: true
            )
      },
      users_permissions: {
            "userId-c": Pubnub::Permission.res(
               get: true
            ),
            "userId-d": Pubnub::Permission.res(
               get: true,
               update: true
            )
      }
   );

Grant an authorized client read access to multiple spaces using RegEx:

The code below grants my-authorized-userId read access to all channels that match the space-[A-Za-z0-9] RegEx pattern.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-userId",
      spaces_permissions: {
            "^space-[A-Za-z0-9]$": Pubnub::Permission.pat(
               read: true
            )
      },
   );

Grant an authorized client different levels of access to various resources and read access to spaces using RegEx in a single call:

The code below grants the my-authorized-userId:

Read access to space-a and userId-c.
Read/write access to space-b, space-c, space-d, and get/update to userId-d.
Read access to all channels that match the space-[A-Za-z0-9] RegEx pattern.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-userId",
      space_permissions: {
            "space-a": Pubnub::Permission.res(
               read: true
            ),
            "space-b": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "space-c": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "space-d": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "^space-[A-Za-z0-9]$": Pubnub::Permission.pat(
               read: true
            )
      },
      users_permissions: {
            "userId-c": Pubnub::Permission.res(
               get: true
            ),
            "userId-d": Pubnub::Permission.res(
               get: true,
               update: true
            )
      }
   );

Error responses

If you submit an invalid request, the server returns the 400 error status code with a descriptive message informing which of the provided arguments is missing or incorrect. These can include, for example, issues with a RegEx, a timestamp, or permissions. The server returns the details of the error in the JSON format.

Revoke Token

Enable token revoke

To revoke tokens, you must first enable this feature on the Admin Portal. To do that, navigate to your app's keyset and mark the Revoke v3 Token checkbox in the ACCESS MANAGER section.

The revoke_token() method allows you to disable an existing token and revoke all permissions embedded within. You can only revoke a valid token previously obtained using the grant_token() method.

Use this method for tokens with ttl less than or equal to 30 days. If you need to revoke a token with a longer ttl, contact support.

For more information, refer to Revoke permissions.

Method(s)

revoke_token(token: token)

Parameter	Type	Required	Default	Description
`token`	`String`	Yes	n/a	Existing token with embedded permissions.

Basic Usage

pubnub.revoke_token("p0thisAkFl043rhDXisRGNoYW6han3Jwsample3KgQ3NwY6BDcGF0pERjaG3BjoERGOAeTyWGJI")

Returns

<Pubnub::Envelope
    @result = {
        :data => {
            "message" => "Success"
        }
    },
    @status = {
        :code => 200
    }
>

Error Responses

If you submit an invalid request, the server returns an error status code with a descriptive message informing which of the provided arguments is missing or incorrect. Depending on the root cause, this operation may return the following errors:

400 Bad Request
403 Forbidden
503 Service Unavailable

Parse Token

The parse_token() method decodes an existing token and returns the object containing permissions embedded in that token. The client can use this method for debugging to check the permissions to the resources or find out the token's ttl details.

Method(s)

parse_token(token: token)

Parameter	Type	Required	Default	Description
`token`	`String`	Yes	n/a	Current token with embedded permissions.

Basic Usage

pubnub.parse_token("p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI")

Returns

{
    "v"=>2,
    "t"=>1627968380,
    "ttl"=>15, 
    "res"=>{
        "chan"=>{
            "channel-1"=>239
        }, 
        "grp"=>{
            "channel_group-1"=>5
        }, 
        "usr"=>{},
        "spc"=>{},
        "uuid"=>{
            "uuid-1"=>104}
        },
    "pat"=>{
        "chan"=>{
            "^channel-\\S*$"=>239
        },
        "grp"=>{
            "^:channel_group-\\S*$"=>5
        },
        "usr"=>{},
        "spc"=>{}, 
        "uuid"=>{
            "^uuid-\\S*$"=>104
        }
    },
    "meta"=>{},
    "uuid"=>"test-authorized-uuid", 
    "sig"=>"\xFAT\xFA\xF0\x9E\xF6\xB9)b\xCF;aJ\xC55i26\xAF\x02V\xF9\x8A\xC0H\xD5\x8Ay\xC3\xAC\x92\\"
}

Error Responses

If you receive an error while parsing the token, it may suggest that the token is damaged. In that case, request the server to issue a new one.

Set Token

The set_token() method is used by the client devices to update the authentication token granted by the server.

Method(s)

set_token(token: token)

Parameter	Type	Required	Default	Description
`token`	`String`	Yes	n/a	Current token with embedded permissions.

Basic Usage

pubnub.set_token("p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI")

Returns

This method doesn't return any response value.

Grant Token (deprecated)

The grant_token() method generates a time-limited authorization token with an embedded access control list. The token defines time to live (ttl), authorized_user_id, and a set of permissions giving access to one or more resources:

channels
channel_groups
uuids (other users' object metadata, such as their names or avatars)

Only this authorized_user_id will be able to use the token with the defined permissions. The authorized client will send the token to PubNub with each request until the token's ttl expires. Any unauthorized request or a request made with an invalid token will return a 403 with a respective error message.

Permissions

The grant request allows your server to securely grant your clients access to the resources within the PubNub Platform. There is a limited set of operations the clients can perform on every resource:

Resource	Permissions
`channel`	`read`, `write`, `get`, `manage`, `update`, `join`, `delete`
`channel_group`	`read`, `manage`
`uuid`	`get`, `update`, `delete`

For permissions and API operations mapping, refer to Manage Permissions with Access Manager v3.

TTL

Recommended `ttl` value

For security reasons, it's recommended to set ttl between 10 and 60, and create a new token before this ttl elapses.

For more details, see TTL in Access Manager v3.

RegEx

For more details, see RegEx in Access Manager v3.

Authorized UUID

Setting an authorized_user_id in the token helps you specify which client device should use this token in every request to PubNub. This will ensure that all requests to PubNub are authorized before PubNub processes them. If authorized_user_id isn't specified during the grant request, the token can be used by any client with any uuid. It's recommended to restrict tokens to a single authorized_user_id to prevent impersonation.

For more details, see Authorized UUID in Access Manager v3.

Method(s)

grant_token(ttl: ttl, authorized_user_id: authorized_user_id, uuids: uuids, channels: channels, channel_groups: channel_groups)

Parameter	Type	Required	Default	Description
`ttl`	`Integer`	Yes	n/a	Total number of minutes for which the token is valid. The minimum allowed value is `1`. The maximum is `43,200` minutes (30 days).
`authorized_user_id`	`String`	Optional	n/a	Single `uuid` which is authorized to use the token to make API requests to PubNub.
`uuids`	`Hash`	Optional	n/a	Hash containing `uuid` metadata permissions provided either as a list or a RegEx pattern, for example: `{"uuid-1": Pubnub::Permissions.res(get: true, update: true, delete: true),"^uuid-2.$": Pubnub::Permissions.pat(...)}`.
`channels`	`Hash`	Optional	n/a	Hash containing channel permissions provided either as a list or a RegEx pattern, for example: `{"channel-1": Pubnub::Permissions.res(read: true, write: true, manage: true, delete: true, get: true, update: true, join: true),"^channel-2.$": Pubnub::Permissions.pat(...)}`.
`channel_groups`	`Hash`	Optional	n/a	Hash containing channel group permissions provided either as a list or a RegEx pattern, for example: `{"group-id-1": Pubnub::Permissions.res(read: true, manage: true),"^group-id-2.$": Pubnub::Permissions.pat(...)}`.
`meta`	`Object`	Optional	n/a	Extra metadata to be published with the request. Values must be scalar only; arrays or objects aren't supported.

Required key/value mappings

For a successful grant request, you must specify permissions for at least one uuid, channel, or channel_groups, either as a resource list or as a pattern (RegEx).

Basic Usage

pubnub.grant_token(
    ttl: 15,
    authorized_user_id: "my-authorized-uuid",
    channels: {
      "my-channel": Pubnub::Permissions.res(
        read: true
      )    
    }
);

Returns

#<Pubnub::Envelope
    @result = {
        :data => {
            "message" => "Success",
            "token" => "p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI"
        }
    },
    @status = {
        :code => 200
    }
>

Other Examples

Grant an authorized client different levels of access to various resources in a single call:

The code below grants my-authorized-uuid:

Read access to channel-a, channel-group-b, and get to uuid-c.
Read/write access to channel-b, channel-c, channel-d, and get/update to uuid-d.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-uuid",
      channels: {
            "channel-a": Pubnub::Permission.res(
               read: true
            ),
            "channel-b": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "channel-c": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "channel-d": Pubnub::Permission.res(
               read: true,
               write: true
            )
      },
      channel_groups: {
            "channel-group-b": Pubnub::Permission.res(
               read: true
            )
      },
      uuids: {
            "uuid-c": Pubnub::Permission.res(
               get: true
            ),
            "uuid-d": Pubnub::Permission.res(
               get: true,
               update: true
            )
      }
   );

Grant an authorized client read access to multiple channels using RegEx:

The code below grants my-authorized-uuid read access to all channels that match the channel-[A-Za-z0-9] RegEx pattern.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-uuid",
      channels: {
            "^channel-[A-Za-z0-9]$": Pubnub::Permission.pat(
               read: true
            )
      },
   );

Grant an authorized client different levels of access to various resources and read access to channels using RegEx in a single call:

The code below grants the my-authorized-uuid:

Read access to channel-a, channel-group-b, and get to uuid-c.
Read/write access to channel-b, channel-c, channel-d, and get/update to uuid-d.
Read access to all channels that match the channel-[A-Za-z0-9] RegEx pattern.

pubnub.grant_token(
      ttl: 15,
      authorized_user_id: "my-authorized-uuid",
      channels: {
            "channel-a": Pubnub::Permission.res(
               read: true
            ),
            "channel-b": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "channel-c": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "channel-d": Pubnub::Permission.res(
               read: true,
               write: true
            ),
            "^channel-[A-Za-z0-9]$": Pubnub::Permission.pat(
               read: true
            )
      },
      channel_groups: {
            "channel-group-b": Pubnub::Permission.res(
               read: true
            )
      },
      uuids: {
            "uuid-c": Pubnub::Permission.res(
               get: true
            ),
            "uuid-d": Pubnub::Permission.res(
               get: true,
               update: true
            )
      }
   );

Grant Token

Recommended ttl value

Method(s)

Required key/value mappings

Basic Usage

Returns

Other Examples

Error responses

Revoke Token

Enable token revoke

Method(s)

Basic Usage

Returns

Error Responses

Parse Token

Method(s)

Basic Usage

Returns

Error Responses

Set Token

Method(s)

Basic Usage

Returns

Grant Token (deprecated)

Recommended ttl value

Method(s)

Required key/value mappings

Basic Usage

Returns

Other Examples

Error responses

Recommended `ttl` value

Recommended `ttl` value