Properties for Device Registration

These properties and their definitions apply to both the user portal and the customer support portal.
account_id Provider's specific users.
actor and actor_type For certain PATCH or DELETE requests, the username of the administrator must be specified in the request body.
auth_token An encrypted string returned to the client in the authorization response. However, in places like a device registration portal you would not do video authorization. To get the auth_token in these cases use the embed token API and specify an additional query parameter return_json=1 to get the response {“auth_token”: “sample_auth_token”}.
device_limit The maximum number of devices that can be registered with the viewer.
next_delete_time The next time a registered device may be deleted from this viewer. ISO 8601 format.
nickname A user friendly name for a device. There are no restrictions on what characters are allowed and the maximum length of a nickname is 255 characters.
pcode Provider code. For details, see Your API Credentials.
public_device_id A random string generated by Ooyala that identifies the device. (This is not the actual ID generated by the Digital Rights Management (DRM) system. The DRM device ID is never exposed.)

See the note below about how the behavior of the Chrome browser can affect the value of the public_device_id.

registration_time The time at which registration was attempted. ISO 8601 format.
result Returned in the response, a specific result of an attempt to register a device. The HTTP response code for most of these messages is 200; be sure to check the response body for specific error messages.
  • 200: new device registered
  • 200: device binding failed
  • 200: device limit reached
  • 200: no device registration action
  • 404: device registration last result not found
user_agent The client’s user agent when the registration attempt was made.

About Google Chrome and Device IDs

Due to restrictions imposed by the Google Chrome browser's architecture for security, your users might experience difficulty with multiple device IDs and device registration. There are two cases:

  • A user who uses two different browsers (one of them Chrome) to register the same physical device will be assigned two different device IDs.
  • Users who reset their Adobe Access DRM licenses in Chrome will lose their device IDs. The IDs will be regenerated the next time DRM content is accessed. Because the user thus has a new device ID, Ooyala's Device Management flow considers it a separate device.

    This condition is best handled by a good design of your user portal and clear information for your customer support group, allowing the user to remove the old device IDs and register the "new" ones.

해당 내용이 도움 되었습니까?