Access Manager v3 API for Java SDK
Access Manager isn't enabled by default
Breaking changes in v9.0.0
PubNub Java SDK version 9.0.0 unifies the codebases for Java and Kotlin SDKs, introduces a new way of instantiating the PubNub client, and changes asynchronous API callbacks and emitted status events. These changes can impact applications built with previous versions (< 9.0.0) of the Java SDK.
For more details about what has changed, refer to Java/Kotlin SDK migration guide.
Gradle compatibility
While older Gradle versions might work, we recommend using Gradle 6.8+ to ensure proper dependency resolution and avoid potential compatibility issues with the SDK's dependencies.
Access Manager allows you to enforce security controls for client access to resources within the PubNub Platform. With Access Manager v3, your servers (that use a PubNub instance configured with a secret key) 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 (
readtochannel1andwritetochannel2).
You can add the authorizedUuid parameter to the grant request to restrict the token usage to one client with a given userId. Once specified, only this authorizedUuid will be able to use the token to make API requests for the specified resources, according to permissions given in the grant request.
User ID / UUID
User ID is also referred to as UUID/uuid in some APIs and server responses but holds the value of the userId parameter you set during initialization.
For more information about Access Manager v3, refer to Manage Permissions with Access Manager v3.
Grant token
Requires Access Manager add-on
This method requires that the Access Manager add-on is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.
Requires Secret Key authentication
Granting permissions to resources should be done by administrators whose SDK instance has been initialized with a Secret Key (available on the Admin Portal on your app's keyset).
The grantToken() method generates a time-limited authorization token with an embedded access control list. The token defines time to live (ttl), authorizedUUID, and a set of permissions giving access to one or more resources:
channelschannelGroupsuuids(other users' object metadata, such as their names or avatars)
Only this authorizedUUID 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
- TTL (time to live)
- RegEx patterns
- Authorized UUID
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 |
|---|---|
channels | read, write, get, manage, update, join, delete |
channelGroups | read, manage |
uuids | get, update, delete |
For permissions and API operations mapping, refer to Manage Permissions with Access Manager v3.
The ttl (time to live) parameter defines how many minutes the permissions remain valid. After expiration, the client must get a new token to maintain access. ttl is required for every grant call. There is no default value. The maximum value is 43,200 (30 days).
For more details, see TTL in Access Manager v3.
Use regular expressions (RegEx) to specify permissions by pattern instead of listing each resource. Set RegEx permissions as patterns before making a grant request. Patterns are evaluated on the server using RE2-style syntax; backreferences and lookaround assertions are not supported.
For more details, see RegEx in Access Manager v3.
Setting an authorizedUUID in the token specifies which client should use this token in every request to PubNub. If authorizedUUID isn't specified during the grant request, the token can be used by any client with any uuid. Restrict tokens to a single authorizedUUID to prevent impersonation.
For more details, see Authorized UUID in Access Manager v3.
Method(s)
1grantToken()
2 .ttl(Integer)
3 .meta(Object)
4 .authorizedUUID(String)
5 .channels(List<ChannelGrant>)
6 .channelGroups(List<ChannelGroupGrant>)
7 .uuids(List<UUIDGrant>)
| Parameter | Description |
|---|---|
ttl *Type: NumberDefault: n/a | Total number of minutes for which the token is valid.
|
metaType: ObjectDefault: n/a | Extra metadata to be published with the request. Values must be scalar only; arrays or objects are not supported. |
authorizedUUIDType: StringDefault: n/a | Single uuid which is authorized to use the token to make API requests to PubNub. |
channelsType: ListDefault: n/a | All channel grants provided either as a list or a RegEx pattern. |
channelGroupsType: ListDefault: n/a | All channel group grants provided either as a list or a RegEx pattern. |
uuidsType: ListDefault: n/a | All uuid grants provided either as a list or a RegEx pattern. |
Required key/value mappings
For a successful grant request, you must specify permissions for at least one uuid, channel, or channelGroup, either as a resource list or as a pattern (RegEx).
Sample code
Reference code
1
Returns
1{"token":"p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI"}
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 touuid-c. - Read/write access to
channel-b,channel-c,channel-d, and get/update touuid-d.
1
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.
1
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-uuid:
- Read access to
channel-a,channel-group-b, and get touuid-c. - Read/write access to
channel-b,channel-c,channel-d, and get/update touuid-d. - Read access to all channels that match the
channel-[A-Za-z0-9]RegEx pattern.
1
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 as a string under the PubNubException class.
Revoke token
Requires Access Manager add-on
This method requires that the Access Manager add-on is enabled for your key in the Admin Portal. Read the support page on enabling add-on features on your keys.
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 revokeToken() 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 grantToken() 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)
1revokeToken()
2 .token(String token)
| Parameter | Description |
|---|---|
token *Type: StringDefault: n/a | Existing token with embedded permissions. |
Sample code
1
Returns
When the token revocation request is successful, this method returns a PNRevokeTokenResult.
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 Request403 Forbidden503 Service Unavailable
Parse token
The parseToken() 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)
1parseToken(String token)
| Parameter | Description |
|---|---|
token *Type: StringDefault: n/a | Current token with embedded permissions. |
Sample code
1
Returns
1
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 setToken() method is used by the client devices to update the authentication token granted by the server.
Method(s)
1setToken(String token)
| Parameter | Description |
|---|---|
token *Type: StringDefault: n/a | Current token with embedded permissions. |
Sample code
1
Returns
This method doesn't return any response value.