DOCSEARCHbyAlgolia
Submit Docs

Axinom Mosaic Documentation

website·Indexed 35 days ago

https://docs.axinom.com

Documentation for the Axinom Mosaic platform, featuring managed services for video encoding, Digital Rights Management (DRM), entitlement management, and user identity. Includes technical guides on the Mosaic Video Service, license service JSON structures, encoding profiles, and platform core technologies like the mosaic-message-bus.

Tokens
313.8K
Snippets
879
Records
2.2K
Agent score
63%

What's inside Axinom

  1. Overview of Axinom Mosaic Localization Service

    The Localization Service (L10n) is a managed service within the Axinom Mosaic suite designed to handle the translation and localization of entities from other services. It focuses on localizing metadata (titles, descriptions, tags, etc.) rather than assets like images or videos.

    Key concepts include:

    • Locales: The service uses 'locales' (e.g., en-US, pt-BR) instead of just 'languages' to account for regional and cultural differences. Users can define their own locales and assign them common names (e.g., 'Brazilian Portuguese').
    • Localizable Fields: Users determine which fields in their data model should be localizable. Textual representations are supported; however, deterministic unit conversions, currency conversions, and date/number formatting should be handled by the client application.
    • Asset Localization: While the service does not localize assets directly, users can create a schema structure to support localized assets (e.g., creating separate 'Poster Image' and 'French Poster Image' types).

  2. Overview of Mosaic Core Services

    Mosaic Core Services provide the foundational infrastructure and operational support for all other services within the platform. The core ecosystem consists of the following services:

    • Identity Service: Handles user authentication and permissions via 3rd party Identity Providers using OAuth 2.0 (e.g., Google).
    • Management System Service: Serves the Management System interface to users.
    • Microfrontend Service: Hosts and serves microfrontends for specific environments to the Management System.
    • RabbitMQ Cluster: Provides the central messaging infrastructure used by all services.
    • Hosting Service: Enables the deployment and hosting of customizable or custom services.

  3. Overview of Axinom Video Platform building blocks

    The Axinom Video Platform is a modular solution for video processing, management, and provisioning. It consists of two primary building blocks:

    • Content/Asset Management: Used to centrally manage video content and editorial workflows.
    • Content Protection: Used to protect content across multiple devices using DRM technologies.

  4. Overview of the mosaic-core base library

    The mosaic-core package is a base library designed to export common types that are shared across various other mosaic libraries and services, ensuring type consistency throughout the mosaic ecosystem.

  5. Overview of the Mosaic Hosting Service Deployment Manifest

    The Deployment Manifest is a configuration document used when deploying services via the Mosaic Hosting Service. It defines the service identity, network exposure, required service accounts, and environment variables. The current supported schema version is '1.0'.
    version: '1.0'
serviceId: media-service

dnsMappedPorts:
  - name: api
    port: 10200

pilets:
  - name: media_workflows
    args:
      MEDIA_SERVICE_BASE_URL: https://${__ax_hosted__.dns.self.api}

serviceAccounts:
  - name: primary
    permissionStructure:
      - serviceId: ax-id-service
        permissions:
          - PERMISSIONS_SYNCHRONIZE
          - ACCESS_TOKENS_GENERATE_LONG_LIVED_TOKEN

regularVariables:
  NODE_ENV: production
  PORT: '${__ax_hosted__.port.api}'

secureVariables:
  DATABASE_OWNER_PASSWORD: '${__ax_hosted__.pg.db_owner_password}'

  6. Overview of Axinom DRM On-board deployment

    Axinom DRM supports disconnected environments (on-board) where internet access is unavailable, such as in-flight entertainment systems, trains, buses, or autonomous kiosks. This is achieved by deploying the DRM License Service as a local Docker container. Supported DRM technologies for on-board deployment include Google Widevine, Apple FairPlay, and Microsoft PlayReady.

  7. Overview of Axinom Image Service

    The Image Service is a Mosaic Managed Service used to manage and transform images for frontend applications. It supports uploading images via UI or GraphQL API, or fetching them from external storage asynchronously. Images are assigned an 'Image Type' and can be optionally tagged. The service provides a microfrontend for management and integrates with the Mosaic Management System, offering extensions for image selection and preview.

  8. Overview of Mosaic User Service migration strategies

    To migrate users from a legacy user store to the Mosaic User Service without forcing password resets or re-authentication, two complementary stages can be used simultaneously:

    1. Session Transfer: Silently moves users who are currently signed in on the legacy system into the User Service without requiring a password.
    2. Lazy Credential Migration: Moves users the first time they attempt to sign in with their email and password through the application.

    Both stages use the user's email address as the unique identifier to ensure no duplicate accounts are created. Migration requires a pre-configured AxAuth standalone user store.

  9. Overview of Axinom Mosaic managed RabbitMQ cluster

    Axinom Mosaic provides a managed RabbitMQ cluster designed for inter-service communication. This cluster allows services within the same environment to communicate with each other as well as with other managed services.

  10. Overview of the Mosaic DRM Service

    The Mosaic DRM Service is a managed service for setting up and operating Axinom DRM within a Mosaic environment. It integrates DRM configuration directly into the Management System, eliminating the need to manually store or copy management keys, key seeds, or FairPlay credentials across different systems. Each environment maintains its own isolated DRM settings to ensure separation between development, test, and production setups.

  11. Overview of Mosaic Delegated Authentication

    Delegated Authentication allows developers to generate a Mosaic End-User Access Token without using the Mosaic User Service for primary authentication. This is used when an application already has its own user management and authentication service but needs to access Mosaic end-user facing services (such as Personalization or Entitlement) which require a Mosaic-issued JWT.

    When a token is generated via Delegated Authentication, the Mosaic User Service creates a user record and profile linked to the provided email address. The resulting token contains the Tenant ID, Environment ID, Application ID, User ID, and Profile ID.

  12. Overview of Axinom Key Service APIs

    The Axinom Key Service is a multi-tenant managed service that provides encryption keys (Content Keys) to packagers for encrypting media assets. It offers two primary APIs:

    1. Key Acquisition API: Used for requesting encryption keys. It supports protocols such as Widevine Common Encryption, SPEKE, Harmonic, and Anevia.
    2. Management API: Used for configuring service behavior, including managing Key Seeds, Content Keys, and importing/exporting keys and logs.