This section describes how the Example Account Service manages access to a user's account, data, or devices.

A Nice Service Provider enables an end user or enterprise to manage their network of Example compliant cameras. This management scope in detail includes:

• Adding cameras to the account.
• Inputting data about the cameras, for example what the camera is looking at.
• Determining which 3rd party apps and services are able to make requests for DeviceModes, access DeviceData, or output feeds from cameras.
• The level of access that 3rd party apps have.

Process:

1. The end user creates an account with a User ID and Account on the App Store provided by the Example Account Service.
2. The Example compliant camera is manufactured with a unique ID and credentials.
3. The user purchasing the Example compliant camera links the camera to their User ID.

The Example Account Service manages a list of cameras that are associated with the user's account and data regarding the capabilities of the cameras and where possible other attributes of the camera such as location, view etc. Access control to any resource associated with a user account is managed through the Example Account Service.

This management is performed in accordance to the OAuth2 standard (RFC 6749) .

• OAuth 2 is used to enable an end user to authorize that an entity or application may access either a camera or DeviceData generated by the camera.
• These credentials may be permanent or limited use depending on the policies selected by the Example Account Service.
• Depending on the configuration of the OAuth token access to the resource by an application or entity may or may not require the Example Account Service to be online or not.