Access Manager v2 API for Python SDK
Access Manager allows you to enforce secure controls for client access to resources within the PubNub network. With Access Manager, your servers can grant their clients access to individual PubNub resources for a limited duration, with the ability to extend access or add permissions for additional resources.
As soon as Access Manager is enabled, no publish/subscribe operations can be done without first explicitly providing an authorization token to the PubNub object. If an invalid token is provided, the requesting client will receive a Forbidden error.
For more information about Access Manager, refer to Managing Permissions with Access Manager.
Grant
Requires Access Manager add-on
This method requires that the Access Manager add-on is enabled for your key in the Admin Portal. See Enable the features your app calls.
The grant method allows you to grant permissions for one or more resources to one or more authKeys. You may need to make multiple grant calls with an authKey so that you can specify explicit permissions for each channel, channelGroup and uuid resources. For common permissions, you can normally use a single request.
Privileges specifically granted to an application's subscribe_key always take precedence over privileges granted to channel or auth_key. Therefore an application that requires authentication at the user level should not grant access at either the Application or Channel levels. View the Grant Levels section for more details.
Permissions
The grant request allows your server to securely grant access for your clients on the following resources within the platform. Each resource allows a limited set of permissions that control the operations that can be performed by the clients. For permissions and API operations mapping information, refer to Managing Permissions with Access Manager
| Resource | Permissions |
|---|---|
channel | read, write, get, manage, update, join, delete |
uuid | get, update, delete |
channelGroup | read, manage |
category (channels, uuids) | get only |
In grant(), categories() selects the channels and uuids categories.
- A category permission lets a token list all metadata of one resource type on your subscribe key. Valid categories are
channelsanduuids. The only permission isget(32). - A
getpermission on one named channel or user, or on a pattern, does not grant a category. - A token can contain only categories. It needs no resource or pattern.
- When enumeration enforcement is enabled for a keyset, App Context list requests from a token or auth key without the matching category permission return a
403error.
Wildcard permissions
Wildcard notation allows you to grant permissions to multiple channels at a time and later revoke these permissions in the same manner. You can only go one level deep using wildcards. In other words:
a.*grants access on all channels that begin witha..*ora.b.*won't work this way. If you grant on*ora.b.*, the grant treats*ora.b.*as a channel name, not a wildcard.
Wildcard revokes
You can revoke permissions with wildcards from one level deep, like a.*, only when you initially used wildcards to grant permissions to a.*.
Grant levels
When a user attempts to access a PubNub resource, Access Manager will evaluate any existing rules using the following order of precedence before access to a channel is granted to the user:
- Application Level - Access Manager privileges are always evaluated first at the
Applicationlevel. If eitherreadorwriteattribute is set toTruefor asubscribe_key, Access Manager will immediately grant access for that attribute without proceeding to check permissions at eitherChannelorUserlevels. If an attribute is set toFalseat the Application level, Access Manager proceeds to evaluate the attribute at the next most granular level. - Channel Level - After first verifying an attribute at the Application level, Access Manager evaluates the attribute at the Channel level. If an attribute is set to
Truefor a combination ofsubscribe_key, andchannel, Access Manager grants access for that attribute at theChannellevel without proceeding to check whether there may beuserlevel permissions. - User Level (Recommended) - As a final step Access Manager evaluates the attributes at the
Userlevel. If an attribute is set toTrueforsubscribe_key,channelandauth_key, access is granted for that attribute. Similarly, user level grants also allow you granting anauth_keyaccess tochannelGroupsanduuids. User level grants requireauth_keyand are the recommended approach if you need to manage permissions for individual users within your application. Each user should be assigned a uniqueauth_keyand securely passed back to the user to perform operations on the platform.
Method(s)
To Grant Permissions on a Channel you can use the following method(s) in the Python SDK:
1pubnub.grant().auth_keys(String|List|Tuple).channels(String|List|Tuple).channel_groups(String|List|Tuple).uuids(String|List|Tuple).categories(String|List|Tuple).read(Boolean).write(Boolean).manage(Boolean).delete(Boolean).get(Boolean).ttl(Int)
auth_keys#- Specifies
authKey to grant permissions. It is possible to specify multipleauthkeys as comma separated list in combination with a singlechannelname. You can also grant access to a singleauthkey for multiplechannelsat the same time. Zero or morechannelswith zero or moreauthtokens are allowed. channels#- Specifies the
channelson which tograntpermissions. If nochannels/channelGroupsare specified, then thegrantapplies to any and allchannels/channelGroupsthat have been or will be created for thatpublish/subscribekey set. Furthermore, any existing or future grants on specificchannelsare ignored, until theall channelsgrant is revoked. It is possible tograntpermissions to multiplechannelssimultaneously by specifying thechannelsas a comma separated list. Wildcard notation likea.*can be used tograntaccess on channels. You cangrantone level deep.a.*- you can grant on this.*anda.b.*- grant will not work on these levels. If you grant on*ora.b.*, the grant will treat*ora.b.*as a single channel named either*ora.b.*.
channel_groups#- Specifies the
channelGroupstograntpermissions. If nochannels/channelGroupsare specified, then thegrantapplies to any and allchannels/channelGroupsthat have been or will be created for thatpublish/subscribekey set. Furthermore, any existing or future grants on specificchannelGroupsare ignored, until theall channelGroupsgrant is revoked. It is possible tograntpermissions to multiplechannelGroupssimultaneously by specifying thechannelGroupsas a comma separated list.
This parameter does not support wildcards. uuids#- Specifies a list of
uuidson which to grant permissions.
You can't grant permissions to channels and channel groups in the same request if you decide to useuuids.
This parameter does not support wildcards. categories#- Specifies the categories to grant. Valid values are
channels, which lists all channel metadata, anduuids, which lists all uuid metadata. Agetpermission on a named channel or uuid doesn't imply this. Requiresauth_keys. Refer to Category permissions. read#Readpermissions.write#Writepermissions.manage#Managepermissions.delete#Deletepermissions.get#Getpermissions.update#Updatepermissions.join#Joinpermissions.ttl#Time to livefor permission to be valid.
Category permissions
- A category permission lets a token list all metadata of one resource type on your subscribe key. Valid categories are
channelsanduuids. The only permission isget(32). - A
getpermission on one named channel or user, or on a pattern, does not grant a category. - A token can contain only categories. It needs no resource or pattern.
- When enumeration enforcement is enabled for a keyset, App Context list requests from a token or auth key without the matching category permission return a
403error.
When you call categories():
- Call
get(True)to grant the category. Callget(False)with the samecategories()andauth_keys()to revoke it. - The SDK leaves out every permission you don't set.
- The
getpermission also applies to every channel, channel group, and uuid in the same request, because all resources in a request share one set of permissions. - Don't set
read,write,manage,delete,update, orjointoTrue.
grant() raises a PubNubException before the SDK sends the request in these cases:
| Cause | Error message |
|---|---|
categories() contains a value other than channels or uuids. | Unsupported categories: <names>. Only 'channels' and 'uuids' are supported |
auth_keys() is missing or empty. | Category grants require providing non empty authKeys |
read, write, manage, delete, update, or join is True. | Category grants allow only the 'get' permission |
get is True and ttl is 1. | One-minute (ttl=1) category grants are not supported |
Sample code
Grant Access Manager permissions for channel and auth_key
1pubnub.grant().channels(["ch1", "ch2", "ch3"]).\
2 channel_groups(["cg1", "cg2"]).\
3 auth_keys(["key1", "key2"]).\
4 read(True).write(True).manage(True).delete(True).\
5 ttl(12337).\
6 sync()
Returns
The grant() operation returns a PNAccessManagerGrantResult which contains the following fields
| Field | Type | Description |
|---|---|---|
level | String | Permissions level, one of subkey, subkey+auth, channel, channel-group, channel-group+auth level. |
ttl | Int | ttl of grant |
subscribe_key | String | The subscribe key. |
channels | Dictionary | Access rights per channel. See PNAccessManagerChannelData for more details. |
groups | Dictionary | Access rights per group. See PNAccessManagerGroupData for more details. |
categories | Dictionary | Category-level access rights, keyed channels and uuids. Each value is a PNAccessManagerCategoryData with the same fields as PNAccessManagerChannelData, where name is the category name. Empty unless you set categories(). |
read_enabled | Boolean | subkey level read permissions. |
write_enabled | Boolean | subkey level write permissions. |
manage_enabled | Boolean | subkey level manage permissions. |
delete_enabled | Boolean | subkey level delete permissions. |
ttl | Int | Time to live value. |
PNAccessManagerChannelData and PNAccessManagerGroupData has the same fields structure
| Field | Type | Description |
|---|---|---|
auth_keys | List | Access rights per auth-key. See PNAccessManagerKeyData for more details. |
name | String | Channel or group name. |
read_enabled | Boolean | Channel or group level read permissions. |
write_enabled | Boolean | Channel or group level write permissions. |
manage_enabled | Boolean | Channel or group level manage permissions. |
delete_enabled | Boolean | Channel or group level delete permissions. |
get | Boolean | Channel, group, or category level get permissions. For a category, this is the only meaningful permission. |
update | Boolean | Channel or group level update permissions. |
join | Boolean | Channel or group level join permissions. |
ttl | Int | Time to live value. |
PNAccessManagerKeyData
| Field | Type | Description |
|---|---|---|
read_enabled | Boolean | read permissions |
write_enabled | Boolean | write permissions |
manage_enabled | Boolean | manage permissions |
delete_enabled | Boolean | delete permissions |
get | Boolean | get permissions |
update | Boolean | update permissions |
join | Boolean | join permissions |
ttl | Int | Time to live value |
read, write, manage, delete, get, update, and join permissions have 3 states:
Trueif enabled.Falseif disabled.Noneif not explicitly set.
Requests size
Access Manager grant or revoke requests must be less than ~32 KiB at a time, or the client will return an error. For requests greater than 32 KiB, break them into smaller batched requests. When the message size exceeds 32 KiB the server returns the HTTP Error code 500, instead of the correct error code 414.
NTP configuration
For NTP synchronization, please ensure that you have configured NTP on your server to keep the clock in sync. This is to prevent system clock drift leading to 400 Invalid Timestamp error response. See Why do I get "Invalid Timestamp" when I grant permissions?.
Other examples
Grant an auth key access to list all channel and uuid metadata
The code below grants my_authkey the get category permission for both channels and uuids, with a 15 minute ttl.
1
Grant subscribe privileges to all users on all channel(s) with default ttl (1440 minutes)
1envelope = pubnub.grant().read(True).write(True).sync()
Allow subscribe and publish to a specific grant subscribe and publish to a specific channel for all users (no auth_key required) with default ttl (1440 minutes)
1envelope = pubnub.grant().channels("my_channel").read(True).write(True).sync()
Grant subscribe access to a channel only for clients with a specific auth_key with a 5 minute ttl
1envelope = pubnub.grant().channels("my_channel").read(True).write(False).\
2 auth_keys("my_ro_authkey").ttl(5).sync()
The above code would return the following response to the client:
1{
2 "status" : 200,
3 "message" : "Success",
4 "payload" : {
5 "ttl" : 5,
6 "auths" : {
7 "my_ro_authkey" : {
8 "r" : 1,
9 "w" : 0,
10 "d" : 0
11 }
12 },
13 "subscribe_key" : "my_subkey",
14 "level" : "user",
15 "channel" : "my_channel"
show all 18 linesAllow access to a specific channel for Presence
1envelope = pubnub.grant().\
2 channels("my_channel-pnpres").read(True).write(True).sync()
Grant Access Manager permissions for channel group
1envelope = pubnub.grant().\
2 channel_groups(["cg1", "cg2", "cg3"]).\
3 auth_keys(["auth1", "auth2", "auth3"]).\
4 read(True).write(True).manage(True).\
5 ttl(12237).\
6 .sync()
The above code would return the following response to the client:
1{
2 "status":200,
3 "message":"Success",
4 "payload":{
5 "ttl":5,
6 "auths":{
7 "my_rw_authkey":{
8 "r":1,
9 "w":1,
10 "d":1
11 }
12 },
13 "subscribe_key":"my_subkey",
14 "level":"user",
15 "channel":"my_channel"
show all 18 linesGrant permissions on multiple channels
1envelope = pubnub.grant().\
2 auth_keys("my_rw_authkey").\
3 channels(["girish", "girish2"]).\
4 read(True).\
5 write(True).\
6 ttl(5).\
7 sync()
Channel limit
The limit on the total amount of channels that you can pass at once when using grant() is 200.
Grant get and update access to a uuid only for clients wit specific AuthKeys with a 24 hr ttl
1envelope = pubnub.grant().uuids("my_uuid").get(True).update(True)
2.auth_keys("my_ro_authkey").ttl(1440).sync()
Application level grant
Use application level grants with caution
When access is granted on an application level, all channels and users will have access.
Application level grants can also happen due to a bug in your code. For example, Null parameters for channels and auth-keys can cause accidental application level grants.
1envelope = pubnub.grant()\
2 read(True).write(True).\
3 .sync()
Channel level grant
1envelope = pubnub.grant().channels("my_channel").\
2 read(True).write(True).\
3 .sync()
User level grant
1envelope = pubnub.grant().channels("my_channel")).\
2 auth_keys("my_authkey").\
3 read(True).write(True).\
4 ttl(5).\
5 .sync()