Networked Media Open Specifications
SPEC... VERSIONS... REPO INFO... TOOLS... IS-... BCP-... MORE... SEARCH

Definitions

←Behaviour - Resource Servers · Index↑ · Upgrade Path→

See also the NMOS Glossary for concepts regarding the JT-NM reference architecture, and definitions within RFCs.

The below definitions are based on the OAuth 2.0 spec.

API

An HTTP/WebSocket Application Programming Interface as defined in an AMWA NMOS Specification (e.g. IS-04, IS-05, IS-06, etc.)

Protected Resource

Any part of the API that is access-restricted. This may apply to read (e.g GET) or write (e.g POST) operations.

Resource Server

The entity that is providing APIs containing protected resources, for example:

Resource Owner / End-User

An entity capable of granting a client access to a protected resource. When the resource owner is a person, it is referred to as an end-user.

Authorization Server

The server hosting the Authorization API. It is responsible for the issuing of authorization codes and Access Tokens to registered clients, after successfully authenticating the client and resource owner and obtaining authorization.

Client

The entity, usually a Web Application, Native application, or SPA (Single Page Application) that is attempting to act on the user’s behalf or access a Protected Resource. A client must register with the Authorization Server before being able to request tokens. Once registered, the client is assigned client credentials in the form of a client_id and, for confidential clients, a client_secret. Clients are usually deemed to be Confidential or Public based on their ability to authenticate securely with the Authorization Server.

Within NMOS this may be:

Access Token

A short-lived JSON Web Token (JWT) that may be used by a client to access Protected Resources on the Resource Server. It consists of a JSON object in which each key:value pair is referred to as a claim.

Bearer Token

A Bearer Token is passed from the Authorization Server to the client after successful authentication of the request. Section 5.1. of RFC 6749 defines it as consisting of:

←Behaviour - Resource Servers · Index↑ · Upgrade Path→