# Authentication
This is the Authentication API Reference.
## Tokens
In the documentation, references to Ably-compatible tokens typically refer either to an Ably Token, or an [Ably JWT](#ably-jwt). For Ably Tokens, this can either be referring to the `TokenDetails` object that contain the `token` string or the token string itself. `TokenDetails` objects are obtained when [requesting an Ably Token](#request-token) from the Ably service and contain not only the `token` string in the `token` attribute, but also contain attributes describing the properties of the Ably Token. For [Ably JWT](#ably-jwt), this will be simply referring to a JWT which has been signed by an Ably private API key.
## Auth object
The principal use-case for the `Auth` object is to create Ably [`TokenRequest`](#token-request) objects with [createTokenRequest](#create-token-request) or obtain [Ably Tokens](#token-details) from Ably with [requestToken](#request-token), and then issue them to other "less trusted" clients. Typically, your servers should be the only devices to have a [private API key](https://ably.com/docs/auth.md#api-key), and this private API key is used to securely sign Ably [`TokenRequest`](#token-request) objects or request [Ably Tokens](#token-details) from Ably. Clients are then issued with these short-lived [Ably Tokens](#token-details) or Ably [`TokenRequest`](#token-request) objects, and the libraries can then use these to authenticate with Ably. If you adopt this model, your private API key is never shared with clients directly.
A subsidiary use-case for the `Auth` object is to preemptively trigger renewal of a token or to acquire a new token with a revised set of capabilities by explicitly calling [`authorize`](#authorize)[`Authorize`](#authorize).
The Auth object is available as the [`auth` field](https://ably.com/docs/api/realtime-sdk.md#auth)[`Auth` property](https://ably.com/docs/api/realtime-sdk.md#auth)[`auth` property](https://ably.com/docs/api/realtime-sdk.md#auth)[`auth` attribute](https://ably.com/docs/api/realtime-sdk.md#auth) of an [Ably Realtime client instance](https://ably.com/docs/api/realtime-sdk.md#constructor).
## Auth Propertiesio.ably.lib.rest.Auth MembersIO.Ably.AblyAuth PropertiesAbly::Auth AttributesARTAuth Properties
The `ART``Auth` object exposes the following public propertiesattributesmembers:
### clientIdclient_idClientId
The client ID string, if any, configured for this client connection. See [identified clients](https://ably.com/docs/auth/identified-clients.md) for more information on trusted client identifiers.
## Auth Methodsio.ably.lib.rest.Auth MethodsIO.Ably.AblyAuth MethodsAbly::Auth MethodsARTAuth Methods
### authorizeAuthorize
`authorize(TokenParams tokenParams?, AuthOptions authOptions?): Promise`
`Deferrable authorize(TokenParams token_params, AuthOptions auth_options) -> yields TokenDetails`
`TokenDetails authorize(TokenParams tokenParams, AuthOptions authOptions)`
`Task AuthorizeAsync(TokenParams?, AuthOptions?)`
`authorize(tokenParams: ARTTokenParams?, authOptions: ARTAuthOptions?, callback: (ARTTokenDetails?, NSError?) -> Void)`
Instructs the library to get a new token immediately. Once fetched, it will upgrade the current realtime connection to use the new token, or if not connected, will initiate a connection to Ably once the new token has been obtained. Also stores any `token_params` and `auth_options``tokenParams` and `authOptions` passed in as the new defaults, to be used for all subsequent implicit or explicit token requests.
Any `token_params` and `auth_options``tokenParams` and `authOptions` objects passed in will entirely replace (as opposed to being merged with) the currently client library saved `token_params` and `auth_options``tokenParams` and `authOptions`.
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| tokenParams | an optional object containing the [token parameters](#token-params)an optional [`TokenParams`](#token-params) object containing the [Ably Token](#token-details) parameters for the authorization request | [`TokenParams`](#token-params) |
| authOptions | an optional object containing the [authentication options](#auth-options)an optional [`TokenParams`](#auth-options) object containing the authentication options for the authorization request | [`AuthOptions`](#auth-options) |
| Parameter | Description | Type |
|-----------|-------------|------|
| token_paramstokenParams | an optional object containing the [token parameters](#token-params)an optional set of key value pairs containing the [token parameters](#token-params) for the authorization request | [`TokenParams`](#token-params) |
| auth_optionsauthOptions | an optional object containing the [authentication options](#auth-options)an optional set of key value pairs containing the [authentication options](#auth-options) for the authorization request | [`AuthOptions`](#auth-options) |
| &blockcallback | yields a [`TokenDetails`](#token-details) objectcalled with a [`ARTTokenDetails`](#token-details) object or an error | |
#### Callback result
On success, the callback will be called with the new [`TokenDetails`](#token-details) object only once the realtime connection has been successfully upgraded to use the new token.
On failure to obtain an token or upgrade the token, the connection will move to the `SUSPENDED` or `FAILED` state, and the callback will be called with `err` containing an `NSError` object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
The `authorize` callback can therefore be used to only trigger an event once the new token has taken effect. This can be useful if, for example, you want to do attach to a new channel following a new channel capability being applied to the connection.
#### Returns
Returns a promise.
On success, the promise is fulfilled with the new [`TokenDetails`](#token-details) once the realtime connection has been successfully upgraded to use the new token.
On failure to obtain a token or upgrade the token, the connection will move to the `SUSPENDED` or `FAILED` state, and the promise will be rejected with an [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Returns
On success, a new [`TokenDetails`](#token-details) is returned only once the realtime connection has been successfully upgraded to use the new [Ably Token](#token-details).
On failure to obtain a token or upgrade the token, the connection will move to the `SUSPENDED` or `FAILED` state and an [`AblyException`](#ably-exception) will be raised with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
The synchronous `authorize` method can therefore be used to run subsequent code only once the new token has taken effect. This can be useful if, for example, you want to do attach to a new channel following a new channel capability being applied to the connection.
#### Returns
Returns a `Task` which needs to be awaited.
On success, a new [`TokenDetails`](#token-details) is returned only once the realtime connection has been successfully upgraded to use the new token.
On failure to obtain a token or upgrade the token, the connection will move to the `SUSPENDED` or `FAILED` state and an [`AblyException`](#ably-exception) will be raised with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
By waiting for the `authorize` method return value, it can be used to run subsequent code only once the new token has taken effect. This can be useful if, for example, you want to do attach to a new channel following a new channel capability being applied to the connection.
#### Returns
A [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) object is returned from this method.
On success, the registered success callbacks for the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) and any block provided to this method yields a [`TokenDetails`](#token-details) only once the realtime connection has been successfully upgraded to use the new token.
On failure to obtain a token or upgrade the token, the connection will move to the `SUSPENDED` or `FAILED` state, triggering the `errback` callbacks of the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) with an [`ErrorInfo`](#error-info) object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
The `authorize` callbacks can therefore be used to trigger an event once the new [Ably Token](#token-details) has taken effect. This can be useful if, for example, you want to do attach to a new channel following a new channel capability being applied to the connection.
#### Example
```javascript
try {
const tokenDetails = await client.auth.authorize({ clientId: 'bob' });
console.log('Success; token: ' + tokenDetails.token);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```nodejs
try {
const tokenDetails = await client.auth.authorize({ clientId: 'bob' });
console.log('Success; token: ' + tokenDetails.token);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```java
try {
TokenParams tokenParams = new TokenParams();
tokenParams.clientId = "bob";
TokenDetails tokenDetails = client.auth.authorize(tokenParams, null);
System.out.println("Success; token = " + tokenDetails.token);
} catch(AblyException e) {
System.out.println("An error occurred; err = " + e.getMessage());
}
```
```csharp
try {
TokenParams tokenParams = new TokenParams {ClientId = "bob"};
TokenDetails tokenDetails = await client.Auth.AuthorizeAsync(tokenParams);
Console.WriteLine("Success; Token = " + tokenDetails.Token);
} catch (AblyException e) {
Console.WriteLine("An error occurred; Error = " + e.Message);
}
```
```ruby
client.auth.authorize(client_id: 'bob') do |token_details|
puts "Success; token = #{token_details.token}"
end
```
```objc
ARTTokenParams *tokenParams = [[ARTTokenParams alloc] initWithClientId:@"Bob"];
[client.auth authorize:tokenParams options:nil callback:^(ARTTokenDetails *tokenDetails, NSError *error) {
if (error) {
NSLog(@"An error occurred; err = %@", error);
} else {
NSLog(@"Success; token = %@", tokenDetails.token);
}
}];
```
```swift
let tokenParams = ARTTokenParams(clientId: "Bob")
client.auth.authorize(tokenParams, options: nil) { tokenDetails, error in
guard let tokenDetails = tokenDetails else {
print("An error occurred; err = \(error!)")
return
}
print("Success; token = \(tokenDetails.token)")
}
```
### createTokenRequestcreate_token_requestCreateTokenRequestAsync
`createTokenRequest(TokenParams tokenParams?, AuthOptions authOptions?): Promise`
`Deferrable create_token_request(TokenParams token_params, AuthOptions auth_options) -> yields TokenRequest`
`TokenRequest createTokenRequest(TokenParams tokenParams, AuthOptions authOptions)`
`Task CreateTokenRequestAsync(TokenParams tokenParams, AuthOptions authOptions)`
`createTokenRequest(tokenParams: ARTTokenParams?, options: ARTAuthOptions?, callback: (ARTTokenRequest?, NSError?) -> Void)`
Creates and signs an Ably [`TokenRequest`](#request-token) based on the specified (or if none specified, the client library stored) `token_params` and `auth_options``tokenParams` and `authOptions`. Note this can only be used when the [API `key`](https://ably.com/docs/auth.md#api-key) value is available locally. Otherwise, the Ably [`TokenRequest`](#request-token) must be obtained from the key owner. Use this to generate Ably [`TokenRequests`](#request-token) in order to implement an [Ably Token](#token-details) request callback for use by other clients.
Both `auth_options` and `token_params``authOptions` and `tokenParams` are optional. When omitted or `null`, the default token parameters and authentication options for the client library are used, as specified in the `ClientOptions` when the client library was instantiated, or later updated with an explicit [`authorize`](#authorize)[`Authorize`](#authorize) request. Values passed in will be used instead of (rather than being merged with) the default values.
To understand why an Ably [`TokenRequest`](#request-token) may be issued to clients in favor of a token, see [Token Authentication explained](https://ably.com/docs/auth/token.md).
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| tokenParams | an optional object containing the [token parameters](#token-params)an optional [`TokenParams`](#token-params) object containing the token parameters for the [Ably Token](#token-details) request | [`TokenParams`](#token-params) |
| authOptions | an optional object containing the [authentication options](#auth-options)an optional [`TokenParams`](#token-params) object containing the authentication options | [`AuthOptions`](#auth-options) |
| Parameter | Description | Type |
|-----------|-------------|------|
| token_paramstokenParams | an optional object containing the [token parameters](#token-params)an optional set of key value pairs containing the [token parameters](#token-params) for the [Ably Token](#token-details) request | [`TokenParams`](#token-params) |
| auth_optionsauthOptions | an optional set of key value pairs containing the [authentication options](#auth-options)an optional [`ARTTokenParams`](#token-params) containing the [authentication options](#auth-options) | [`AuthOptions`](#auth-options) |
| &blockcallback | yields a [`TokenRequest`](#token-request) objectcalled with a [`ARTTokenRequest`](#token-request) object or an error | |
#### Returns
Returns a promise.
On success, the promise is fulfilled with the new [`TokenRequest`](#token-request) JSON object
On failure to issue a [`TokenRequest`](#token-request), the promise is rejected with an [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Returns
On success, a [`TokenRequest`](#token-request) object is returned.
Failure to issue a [`TokenRequest`](#token-request) will raise an [`AblyException`](#ably-exception).
#### Returns
Returns a `Task` which needs to be awaited.
On success, a [`TokenRequest`](#token-request) object is returned.
Failure to issue a [`TokenRequest`](#token-request) will raise an [`AblyException`](#ably-exception).
#### Returns
A [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) object is returned from this method.
On success, the registered success callbacks for the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) and any block provided to this method yields a [`TokenRequest`](#token-request) object.
Failure to issue a [`TokenRequest`](#token-request) will trigger the errback callbacks of the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) with an [`ErrorInfo`](#error-info) object containing an error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Example
```javascript
try {
const tokenRequest = await client.auth.createTokenRequest({ clientId: 'bob' });
console.log('Success; token request = ' + tokenRequest);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```nodejs
try {
const tokenRequest = await client.auth.createTokenRequest({ clientId: 'bob' });
console.log('Success; token request = ' + tokenRequest);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```java
try {
TokenParams tokenParams = new TokenParams();
tokenParams.clientId = "bob";
TokenRequest tokenRequest = client.auth.createTokenRequest(tokenParams, null);
System.out.println("Success; token request issued");
} catch(AblyException e) {
System.out.println("An error occurred; err = " + e.getMessage());
}
```
```csharp
try {
TokenParams tokenParams = new TokenParams {ClientId = "bob"};
TokenRequest tokenRequest = await client.Auth.CreateTokenRequestAsync(tokenParams);
Console.WriteLine("Success; token request issued");
} catch (AblyException e) {
Console.WriteLine("An error occurred; err = " + e.Message);
}
```
```ruby
client.auth.create_token_request(client_id: 'bob') do |token_request|
puts "Success; token request = #{token_request}"
end
```
```objc
ARTTokenParams *tokenParams = [[ARTTokenParams alloc] initWithClientId:@"Bob"];
[client.auth createTokenRequest:tokenParams options:nil callback:^(ARTTokenRequest *tokenRequest, NSError *error) {
if (error) {
NSLog(@"An error occurred; err = %@", error);
} else {
NSLog(@"Success; token request = %@", tokenRequest);
}
}];
```
```swift
let tokenParams = ARTTokenParams(clientId: "Bob")
client.auth.createTokenRequest(tokenParams, options: nil) { tokenRequest, error in
guard let tokenRequest = tokenRequest else {
print("An error occurred; err = \(error!)")
return
}
print("Success; token request = \(tokenRequest)")
}
```
### requestTokenrequest_tokenRequestTokenAsync
`requestToken(TokenParams tokenParams?, AuthOptions authOptions?): Promise`
`Deferrable request_token(TokenParams token_params, AuthOptions auth_options) -> yields TokenDetails`
`TokenDetails requestToken(TokenParams tokenParams, AuthOptions authOptions)`
`async Task RequestTokenAsync(TokenParams? tokenParams, AuthOptions? options)`
`requestToken(tokenParams: ARTTokenParams?, withOptions: ARTAuthOptions?, callback: (ARTTokenDetails?, NSError?) -> Void)`
Calls the [`requestToken` REST API endpoint](https://ably.com/docs/api/rest-api.md#request-token) to obtain an [Ably Token](#token-details) according to the specified `token_params` and `auth_options``tokenParams` and `authOptions`.
Both `auth_options` and `token_params``authOptions` and `tokenParams` are optional. When omitted or `null`, the default token parameters and authentication options for the client library are used, as specified in the `ClientOptions` when the client library was instantiated, or later updated with an explicit [`authorize`](#authorize)[`Authorize`](#authorize) request. Values passed in will be used instead of (rather than being merged with) the default values.
To understand why an Ably [`TokenRequest`](#request-token) may be issued to clients in favor of a token, see [Token Authentication explained](https://ably.com/docs/auth/token.md).
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| tokenParams | an optional object containing the [token parameters](#token-params)an optional [`TokenParams`](#token-params) object containing the token parameters for the requested token | [`TokenParams`](#token-params) |
| authOptions | an optional object containing the [authentication options](#auth-options)an optional [`TokenParams`](#auth-options) object containing the authentication options for the requested [Ably Token](#token-details) | [`AuthOptions`](#auth-options) |
| Parameter | Description | Type |
|-----------|-------------|------|
| token_paramstokenParams | an optional object containing the [token parameters](#token-params)an optional set of key value pairs containing the [token parameters](#token-params) for the requested token | [`TokenParams`](#token-params) |
| auth_optionsauthOptions | an optional object containing the [authentication options](#auth-options)an optional set of key value pairs containing the [authentication options](#auth-options) for the requested [Ably Token](#token-details) | [`AuthOptions`](#auth-options) |
| &blockcallback | yields a [`TokenDetails`](#token-details) objectcalled with a [`ARTTokenDetails`](#token-details) object or an error | |
#### Returns
Returns a promise.
On success, the promise is fulfilled with a [`TokenDetails`](#token-details) object containing the details of the new [Ably Token](#token-details) along with the `token` string.
On failure to obtain an [Ably Token](#token-details), the promise is rejected with an [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Callback result
On success, `tokenDetails` contains a [`TokenDetails`](#token-details) object containing the details of the new [Ably Token](#token-details) along with the `token` string.
On failure to obtain an [Ably Token](#token-details), `err` contains an [`ErrorInfo`](#error-info)`NSError` object with an error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Returns
On success, a [`TokenDetails`](#token-details) object containing the details of the new [Ably Token](#token-details) along with the `token` string is returned.
Failure to obtain an [Ably Token](#token-details) will raise an [`AblyException`](#ably-exception).
#### Returns
Returns a `Task` which needs to be awaited.
On success, a [`TokenDetails`](#token-details) object containing the details of the new [Ably Token](#token-details) along with the `token` string is returned.
Failure to obtain an [Ably Token](#token-details) will raise an [`AblyException`](#ably-exception).
#### Returns
A [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) object is returned from this method.
On success, the registered success callbacks for the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) and any block provided to this method yields a [`TokenDetails`](#token-details) object containing the details of the new [Ably Token](#token-details) along with the `token` string.
Failure to obtain an [Ably Token](#token-details) will trigger the errback callbacks of the [`Deferrable`](https://ably.com/docs/api/realtime-sdk/types.md#deferrable) with an [`ErrorInfo`](#error-info) object containing an error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Example
```javascript
try {
const tokenDetails = await client.auth.requestToken({ clientId: 'bob'});
console.log('Success; token = ' + tokenDetails.token);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```nodejs
try {
const tokenDetails = await client.auth.requestToken({ clientId: 'bob'});
console.log('Success; token = ' + tokenDetails.token);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```ruby
client.auth.request_token(client_id: 'bob') do |token_details|
puts "Success; token = #{token_details.token}"
end
```
```java
try {
TokenParams tokenParams = new TokenParams();
tokenParams.clientId = "bob";
TokenDetails tokenDetails = client.auth.requestToken(tokenParams, null);
System.out.println("Success; token = " + tokenDetails.token);
} catch(AblyException e) {
System.out.println("An error occurred; err = " + e.getMessage());
}
```
```csharp
try {
TokenParams tokenParams = new TokenParams {ClientId = "bob"};
TokenDetails tokenDetails = await client.Auth.RequestTokenAsync(tokenParams);
Console.WriteLine("Success; token = " + tokenDetails.Token);
} catch (AblyException e) {
Console.WriteLine("An error occurred; err = " + e.Message);
}
```
```objc
ARTTokenParams *tokenParams = [[ARTTokenParams alloc] initWithClientId:@"Bob"];
[client.auth requestToken:tokenParams withOptions:nil callback:^(ARTTokenDetails *tokenDetails, NSError *error) {
if (error) {
NSLog(@"An error occurred; err = %@", error);
} else {
NSLog(@"Success; token = %@", tokenDetails.token);
}
}];
```
```swift
let tokenParams = ARTTokenParams(clientId: "Bob")
client.auth.requestToken(tokenParams, withOptions: : nil) { tokenDetails, error in
guard let tokenDetails = tokenDetails else {
print("An error occurred; err = \(error!)")
return
}
print("Success; token = \(tokenDetails.token)")
}
```
### revokeTokens
`revokeTokens(TokenRevocationTargetSpecifier[] specifiers, TokenRevocationOptions options?): Promise>`
Calls the [`revokeTokens` REST API endpoint](https://ably.com/docs/api/rest-api.md#revoke-tokens) to revoke tokens specified by the provided array of [TokenRevocationTargetSpecifier](#token-revocation-target-specifier).
Only tokens issued by an API key that had revocable tokens enabled before the token was issued can be revoked. See the [token revocation docs](https://ably.com/docs/auth/revocation.md) for more information.
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| specifiers | an array of [TokenRevocationTargetSpecifier](#token-revocation-target-specifier) objects | [`TokenRevocationTargetSpecifier[]`](#token-revocation-target-specifier) |
| options | an optional set of options which are used to modify the revocation request | [`TokenRevocationOptions`](#token-revocation-options) |
#### Returns
Returns a promise.
On success, the promise is fulfilled with a [BatchResult](#batch-result) containing information about the result of the token revocation request for each provided [TokenRevocationTargetSpecifier](#token-revocation-target-specifier).
On failure, the promise is rejected with an [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) object with the error response as defined in the [Ably REST API](https://ably.com/docs/api/rest-api.md#common) documentation.
#### Example
```javascript
try {
const response = await client.auth.revokeTokens([{ type: 'clientId', value: 'bob' }]);
console.log('Revocation successful; revoked tokens: ' + response.results.length);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
```nodejs
try {
const response = await client.auth.revokeTokens([{ type: 'clientId', value: 'bob' }]);
console.log('Revocation successful; revoked tokens: ' + response.results.length);
} catch (error) {
console.log('An error occurred; err = ' + error.message);
}
```
## Related types
### AuthOptions ObjectARTAuthOptionsAuthOptions Hashio.ably.lib.rest.Auth.AuthOptions
`AuthOptions` is a plain JavaScript object and is used when making [authentication](https://ably.com/docs/auth.md) requests. If passed in, an `authOptions` object will be used instead of (as opposed to supplementing or being merged with) the default values given when the library was instantiated. The following attributes are supported:
`AuthOptions` is a Hash object and is used when making [authentication](https://ably.com/docs/auth.md) requests. These options will supplement or override the corresponding options given when the library was instantiated. The following key symbol values can be added to the Hash:
`ARTAuthOptions` is used when making [authentication](https://ably.com/docs/auth.md) requests. These options will supplement or override the corresponding options given when the library was instantiated.
`AuthOptions` is used when making [authentication](https://ably.com/docs/auth.md) requests. These options will supplement or override the corresponding options given when the library was instantiated.
#### PropertiesMembersAttributes
| Property | Description | Type |
|----------|-------------|------|
| authCallbackAuthCallback:auth_callback | A functionfunction with the form `function(tokenParams, callback(err, tokenOrTokenRequest))``TokenCallback` instanceproc / lambda (called synchronously in REST and Realtime but does not block EventMachine in the latter) which is called when a new token is required. The role of the callback is to obtain a fresh token, one of: an Ably Token string (in plain text format); a signed [`TokenRequest`](https://ably.com/docs/api/realtime-sdk/types.md#token-request) ; a [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) (in JSON format); an [Ably JWT](https://ably.com/docs/api/realtime-sdk/authentication.md#ably-jwt). See [our authentication documentation](https://ably.com/docs/auth.md) for details of the Ably TokenRequest format and associated API calls. | `Callable``TokenCallback``Proc``Func>` |
| authUrlAuthUrl:auth_url | A URL that the library may use to obtain a fresh token, one of: an Ably Token string (in plain text format); a signed [`TokenRequest`](https://ably.com/docs/api/realtime-sdk/types.md#token-request) ; a [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) (in JSON format); an [Ably JWT](https://ably.com/docs/api/realtime-sdk/authentication.md#ably-jwt). For example, this can be used by a client to obtain signed Ably TokenRequests from an application server. | `String``Uri``NSURL` |
| authMethodAuthMethod:auth_method | _`GET``:get`_ The HTTP verb to use for the request, either `GET``:get` or `POST``:post` | `String``Symbol``HttpMethod` |
| authHeadersAuthHeaders:auth_headers | A set of key value pair headers to be added to any request made to the `authUrl``AuthUrl`. Useful when an application requires these to be added to validate the request or implement the response. If the `authHeaders` object contains an `authorization` key, then `withCredentials` will be set on the xhr request. | `Object``Hash``Param []``Dictionary` |
| authParamsAuthParams:auth_params | A set of key value pair params to be added to any request made to the `authUrl``AuthUrl`. When the `authMethod``AuthMethod` is `GET`, query params are added to the URL, whereas when `authMethod``AuthMethod` is `POST`, the params are sent as URL encoded form data. Useful when an application require these to be added to validate the request or implement the response. | `Object``Hash``Param[]``Dictionary``NSArray``[NSURLQueryItem]/Array` |
| tokenDetailsTokenDetails:token_details | An authenticated [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) object (most commonly obtained from an Ably Token Request response). This option is mostly useful for testing: since tokens are short-lived, in production you almost always want to use an authentication method that allows the client library to renew the token automatically when the previous one expires, such as `authUrl``AuthUrl``:auth_url` or `authCallback`AuthCallback`auth_callback``:auth_callback`. Use this option if you wish to use Token authentication. Read more about [Token authentication](https://ably.com/docs/auth/token.md) | `TokenDetails` |
| keyKey:key | Optionally the [API key](https://ably.com/docs/auth.md#api-key) to use can be specified as a full key string; if not, the API key passed into [`ClientOptions`](#client-options) when instancing the Realtime or REST library is used | `String` |
| queryTimeQueryTime:query_time | _false_ If true, the library will query the Ably servers for the current time when [issuing TokenRequests](https://ably.com/docs/auth/token.md) instead of relying on a locally-available time of day. Knowing the time accurately is needed to create valid signed Ably [TokenRequests](https://ably.com/docs/auth/token.md), so this option is useful for library instances on auth servers where for some reason the server clock cannot be kept synchronized through normal means, such as an [NTP daemon](https://en.wikipedia.org/wiki/Ntpd) . The server is queried for the current time once per client library instance (which stores the offset from the local clock), so if using this option you should avoid instancing a new version of the library for each request. | `Boolean` |
| tokenToken:token | An authenticated token. This can either be a [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) object, a [`TokenRequest`](https://ably.com/docs/api/realtime-sdk/types.md#token-request) object, or token string (obtained from the `token``Token` property of a [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) component of an Ably TokenRequest response, or a [JSON Web Token](https://tools.ietf.org/html/rfc7519) satisfying [the Ably requirements for JWTs](https://ably.com/docs/auth/token.md#jwt)). This option is mostly useful for testing: since tokens are short-lived, in production you almost always want to use an authentication method that allows the client library to renew the token automatically when the previous one expires, such as `authUrl`AuthUrl:auth_urlauth_url or authCallbackAuthCallbackauth_callback:auth_callback. Read more about [Token authentication](https://ably.com/docs/auth/token.md) | `String`, `TokenDetails` or `TokenRequest` |
### TokenDetails ObjectARTTokenDetailsio.ably.lib.types.TokenDetailsAbly::Models::TokenDetailsIO.Ably.TokenDetails
`TokenDetails` is a type providing details of Ably Token string and its associated metadata.
#### PropertiesMembersAttributes
| Property | Description | Type |
|----------|-------------|------|
| tokenToken | The [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) itself. A typical [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) string may appear like `{{TOKEN}}` | `String` |
| expiresExpires | The time (in milliseconds since the epoch)The time at which this token expires | `Integer``Long Integer``DateTimeOffset``Time``NSDate` |
| issuedIssued | The time (in milliseconds since the epoch)The time at which this token was issued | `Integer``Long Integer``DateTimeOffset``Time``NSDate` |
| capabilityCapability | The capability associated with this [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). The capability is a a JSON stringified canonicalized representation of the resource paths and associated operations. [Read more about authentication and capabilities](https://ably.com/docs/auth/capabilities.md) | `String``Capability` |
| clientIdclient_idClientId | The client ID, if any, bound to this [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). If a client ID is included, then the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) authenticates its bearer as that client ID, and the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) may only be used to perform operations on behalf of that client ID. The client is then considered to be an [identified client](https://ably.com/docs/auth/identified-clients.md) | `String` |
### Methods
| Method | Description | Type |
|--------|-------------|------|
| expired? | True when the token has expired | `Boolean` |
### Methods
| Method | Description | Type |
|--------|-------------|------|
| IsValidToken() | True if the token has not expired | `Boolean` |
### TokenDetails constructors
#### TokenDetails.fromJsonTokenDetails.from_json
`TokenDetails.fromJson(String json) -> TokenDetails`
`TokenDetails.from_json(String json) -> TokenDetails`
A static factory method to create a [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) from a deserialized `TokenDetails`-like object or a JSON stringified `TokenDetails`. This method is provided to minimize bugs as a result of differing types by platform for fields such as `timestamp` or `ttl`. For example, in Ruby `ttl` in the `TokenDetails` object is exposed in seconds as that is idiomatic for the language, yet when serialized to JSON using `to_json` it is automatically converted to the Ably standard which is milliseconds. By using the `fromJson` method when constructing a `TokenDetails`, Ably ensures that all fields are consistently serialized and deserialized across platforms.
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| json | a `TokenDetails`-like deserialized object or JSON stringified `TokenDetails`. | `Object`, `String` |
#### Returns
A [`TokenDetails`](https://ably.com/docs/api/realtime-sdk/types.md#token-details) object
### TokenParams ObjectARTTokenParamsTokenParams Hashio.ably.lib.rest.Auth.TokenParamsIO.Ably.TokenParams
`TokenParams` is a plain JavaScript object and is used in the parameters of [token authentication](https://ably.com/docs/auth/token.md) requests, corresponding to the desired attributes of the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). The following attributes can be defined on the object:
`TokenParams` is a Hash object and is used in the parameters of [token authentication](https://ably.com/docs/auth/token.md) requests, corresponding to the desired attributes of the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). The following key symbol values can be added to the Hash:
`TokenParams` is used in the parameters of [token authentication](https://ably.com/docs/auth/token.md) requests, corresponding to the desired attributes of the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details).
`ARTTokenParams` is used in the parameters of [token authentication](https://ably.com/docs/auth/token.md) requests, corresponding to the desired attributes of the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details).
#### PropertiesMembersAttributes
| Property | Description | Type |
|----------|-------------|------|
| capabilityCapability:capability | JSON stringified capability of the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). If the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) request is successful, the capability of the returned [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) will be the intersection of this capability with the capability of the issuing key. [Find our more about how to use capabilities to manage access privileges for clients](https://ably.com/docs/auth/capabilities.md). | `String``Capability` |
| clientIdClientIdclient_id:client_id | A client ID, used for identifying this client when publishing messages or for presence purposes. The `clientId``client_id``ClientId` can be any non-empty string. This option is primarily intended to be used in situations where the library is instantiated with a key; note that a `clientId``client_id``ClientId` may also be implicit in a token used to instantiate the library; an error will be raised if a `clientId``client_id``ClientId` specified here conflicts with the `clientId``client_id``ClientId` implicit in the token. [Find out more about client identities](https://ably.com/docs/auth/identified-clients.md) | `String` |
| nonceNonce:nonce | An optional opaque nonce string of at least 16 characters to ensure uniqueness of this request. Any subsequent request using the same nonce will be rejected. | `String` |
| timestampTimestamp:timestamp | The timestamp (in milliseconds since the epoch)The timestamp of this request. `timestamp`, in conjunction with the `nonce`, is used to prevent requests for [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) from being replayed. | `Integer``Long Integer``Time``NSDate``DateTimeOffset``DateTime` |
| ttlTtl:ttl | Requested time to live for the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) being created in millisecondsin secondsas a `NSTimeInterval`as a `TimeSpan`. When omitted, the Ably REST API default of 60 minutes is applied by Ably.
_Default: 1 hour_ | `Integer` (milliseconds)`Integer` (seconds)`NSTimeInterval``Long Integer``TimeSpan` |
### TokenRequest ObjectARTTokenRequestAbly::Models::TokenRequestio.ably.lib.rest.Auth.TokenRequestIO.Ably.TokenRequest
`TokenRequest` is a type containing parameters for an Ably `TokenRequest`. [Ably Tokens](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) are requested using [Auth#requestToken](https://ably.com/docs/api/rest-sdk/authentication.md#request-token)[Auth#request_token](https://ably.com/docs/api/rest-sdk/authentication.md#request-token)
#### PropertiesMembersAttributes
| Property | Description | Type |
|----------|-------------|------|
| keyNamekey_nameKeyName | The key name of the key against which this request is made. The key name is public, whereas the key secret is private | `String` |
| ttlTtl | Requested time to live for the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) in millisecondsin secondsas a `TimeSpan`. If the Ably `TokenRequest` is successful, the TTL of the returned [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) will be less than or equal to this value depending on application settings and the attributes of the issuing key. | `Integer``TimeSpan``NSTimeInterval` |
| timestampTimestamp | The timestamp of this request in milliseconds | `Integer``Long Integer``Time``DateTimeOffset``NSDate` |
| capabilityCapability | Capability of the requested [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). If the Ably `TokenRequest` is successful, the capability of the returned [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) will be the intersection of this capability with the capability of the issuing key. The capability is a JSON stringified canonicalized representation of the resource paths and associated operations. [Read more about authentication and capabilities](https://ably.com/docs/auth.md) | `String` |
| clientIdclient_idClientId | The client ID to associate with the requested [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details). When provided, the [Ably Token](https://ably.com/docs/api/realtime-sdk/authentication.md#token-details) may only be used to perform operations on behalf of that client ID | `String` |
| nonceNonce | An opaque nonce string of at least 16 characters | `String` |
| macMac | The Message Authentication Code for this request | `String` |
### TokenRequest constructors
#### TokenRequest.fromJsonTokenRequest.from_jsonTokenRequest.fromMap
`TokenRequest.fromJson(String json) -> TokenRequest`
`TokenRequest.from_json(String json) -> TokenRequest`
A static factory method to create a [`TokenRequest`](https://ably.com/docs/api/realtime-sdk/types.md#token-request) from a deserialized `TokenRequest`-like object or a JSON stringified `TokenRequest`. This method is provided to minimize bugs as a result of differing types by platform for fields such as `timestamp` or `ttl`. For example, in Ruby `ttl` in the `TokenRequest` object is exposed in seconds as that is idiomatic for the language, yet when serialized to JSON using `to_json` it is automatically converted to the Ably standard which is milliseconds. By using the `fromJson` method when constructing a `TokenRequest`, Ably ensures that all fields are consistently serialized and deserialized across platforms.
#### Parameters
| Parameter | Description | Type |
|-----------|-------------|------|
| json | a `TokenRequest`-like deserialized object or JSON stringified `TokenRequest`. | `Object`, `String` |
#### Returns
A [`TokenRequest`](https://ably.com/docs/api/realtime-sdk/types.md#token-request) object
### Ably JWT
An Ably JWT is not strictly an Ably construct, rather it is a [JWT](https://jwt.io/) which has been constructed to be compatible with Ably. The JWT must adhere to the following to ensure compatibility:
| Section | Field | Required | Description |
|---------|-------|----------|-------------|
| JOSE header | `kid` | Yes | Key name, such that an API key of `your-api-key` will have key name `{{API_KEY_NAME}}` |
| JWT claim set | `iat` | Yes | Time of issue in seconds |
| JWT claim set | `exp` | Yes | Expiry time in seconds |
| JWT claim set | `x-ably-capability` | No | JSON text encoding of the [capability](#tokens) |
| JWT claim set | `x-ably-clientId` | No | Client ID |
Arbitrary additional claims and headers are supported (apart from those prefixed with `x-ably-` which are reserved for future use).
The Ably JWT must be signed with the secret part of your [Ably API key](https://ably.com/docs/auth.md#api-key) using the signature algorithm HS256 (HMAC using the SHA-256 hash algorithm). View the [JSON Web Algorithms (JWA) specification](https://tools.ietf.org/html/rfc7518) for further information.
We recommend you use one of the many [JWT libraries available for simplicity](https://jwt.io/) when creating your JWTs.
The following is an example of creating an Ably JWT:
```javascript
var header = {
"typ":"JWT",
"alg":"HS256",
"kid": "{{API_KEY_NAME}}"
};
var currentTime = Math.round(Date.now()/1000);
var claims = {
"iat": currentTime, /* current time in seconds */
"exp": currentTime + 3600, /* time of expiration in seconds */
"x-ably-capability": "{\"*\":[\"*\"]}"
};
var base64Header = btoa(header);
var base64Claims = btoa(claims);
/* Apply the hash specified in the header */
var signature = hash((base64Header + "." + base64Claims), "{{API_KEY_SECRET}}");
var ablyJwt = base64Header + "." + base64Claims + "." + signature;
```
*Note:* At present Ably does not support asymmetric signatures based on a keypair belonging to a third party.
### BatchResult
A `BatchResult` contains information about the results of a batch operation.
#### Properties
| Property | Description | Type |
|----------|-------------|------|
| successCount | The number of successful operations in the request | `Number` |
| failureCount | The number of unsuccessful operations in the request | `Number` |
| messages | An array of results for the batch operation (for example, an array of [`BatchPublishSuccessResult`](https://ably.com/docs/api/realtime-sdk/types.md#batch-publish-success-result) or [`BatchPublishFailureResult`](https://ably.com/docs/api/realtime-sdk/types.md#batch-publish-failure-result) for a channel batch publish request) | `Object[]` |
### TokenRevocationTargetSpecifier
A `TokenRevocationTargetSpecifier` describes which tokens should be affected by a token revocation request.
#### Properties
| Property | Description | Type |
|----------|-------------|------|
| type | The type of token revocation target specifier. Valid values include `clientId`, `revocationKey` and `channel` | `String` |
| value | The value of the token revocation target specifier | `String` |
### TokenRevocationOptions
A `TokenRevocationOptions` describes the additional options accepted by revoke tokens request.
#### Properties
| Property | Description | Type |
|----------|-------------|------|
| issuedBefore | An optional Unix timestamp in milliseconds where only tokens issued before this time are revoked. The default is the current time. Requests with an `issuedBefore` in the future, or more than an hour in the past, will be rejected | `Number` |
| allowReauthMargin | _false_ If true, permits a token renewal cycle to take place without needing established connections to be dropped, by postponing enforcement to 30 seconds in the future, and sending any existing connections a hint to obtain (and upgrade the connection to use) a new token. The default is `false`, meaning that the effect is near-immediate. | `Boolean` |
### TokenRevocationSuccessResult
A `TokenRevocationSuccessResult` contains information about the result of a successful token revocation request for a single target specifier.
#### Properties
| Property | Description | Type |
|----------|-------------|------|
| target | The target specifier | `String` |
| appliesAt | The time at which the token revocation will take effect, as a Unix timestamp in milliseconds | `Number` |
| issuedBefore | A Unix timestamp in milliseconds. Only tokens issued earlier than this time will be revoked | `Number` |
### TokenRevocationFailureResult
A `TokenRevocationFailureResult` contains information about the result of an unsuccessful token revocation request for a single target specifier.
#### Properties
| Property | Description | Type |
|----------|-------------|------|
| target | The target specifier | `String` |
| error | Describes the reason for which token revocation failed for the given `target` as an [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) object | [`ErrorInfo`](https://ably.com/docs/api/realtime-sdk/types.md#error-info) |