Meta tags:
description=The CPIX V2.0 specification allows for any elements with an ID be to signed and verified. This feature allows packagers to sign the CPIX request as an alternate form of authentication. Both document signing and key encryption must be supported by packagers in order to remove the requirement for JWT…;

Headings (most frequently used words):

streamkeeper, cpix, enhanced, security, api, multi, drm, faqs, verimatrix, platform, what, next,

Text of the page (most frequently used words):
cpix (15), the (14), app (14), for (12), your (12), and (10), streamkeeper (10), drm (10), api (8), status (8), codes (8), counterspy (8), #verimatrix (7), key (7), security (7), multi (7), dashboard (7), use (6), content (6), document (6), client (6), ios (6), with (5), authentication (5), enhanced (5), widevine (5), android (5), create (4), encryption (4), signing (4), service (4), activity (4), case (4), fairplay (4), claims (4), specification (3), signed (3), request (3), supported (3), platform (3), getting (3), started (3), deepscan (3), reveal (3), integration (3), playready (3), authorization (3), test (3), data (3), protection (3), guides (3), all (2), privacy (2), terms (2), com (2), page (2), this (2), signature (2), information (2), allows (2), packagers (2), sign (2), packager (2), that (2), can (2), guide (2), managing (2), drms (2), frequently (2), asked (2), questions (2), faqs (2), monitoring (2), watermarking (2), faq (2), certificate (2), setup (2), specific (2), token (2), overview (2), view (2), troubleshooting (2), protecting (2), preparing (2), talk (2), 2025, rights, reserved, notice, www, copy, did, help, you, yes, what, next, updated, over, year, ago, digital, more, refer, any, elements, verified, feature, alternate, form, both, must, order, remove, requirement, jwt, expected, authenticate, following, xml, syntax, processing, version, turn, signs, response, verify, trial, secure, delivery, setting, sso, risk, detections, quick, multifactor, mfa, user, roles, users, how, three, major, identify, devices, google, decryption, module, cdm, license, handling, billing, models, omi, ott, iptv, vcas, live, rotation, apple, streaming, hdcp, compatibility, best, practices, query, parameters, application, generation, hardening, requirements, system, player, package, encrypt, consumer, playback, generate, tokens, configure, access, tiers, comparison, email, alerting, usage, description, retention, event, management, siem, gdpr, liveboost, build, automation, features, platforms, registered, apps, table, testing, protected, threat, responses, threat_responses, custom_protection, generating, developer, uploading, building, introduction, interface, search, home, jump, agents, visit, https, docs, llms, txt, index, pages, formatted, markdown, endpoints, openapi,

Text of the page (random words):
cpix enhanced security api verimatrix streamkeeper counterspy faqs for ai agents visit https docs verimatrix com llms txt for an index of all pages formatted in markdown and endpoints in openapi jump to content home guides talk to us guides search talk to us guides cpix enhanced security api cpix enhanced security api streamkeeper streamkeeper counterspy getting started with counterspy protection introduction to the counterspy interface counterspy for android preparing your android app building your app uploading your app protecting your android app generating an app signing certificate for a developer signed app signing your android app test your app troubleshooting your android app protection custom_protection threat_responses threat responses counterspy for ios preparing your ios app protecting an ios app signing your ios app testing your protected ios app troubleshooting your ios app protection counterspy dashboard getting started with dashboard dashboard view table view managing registered apps features and supported platforms build automation ci cd integration liveboost api faq data privacy and gdpr security information and event management siem integration data retention data description api usage email alerting counterspy tiers comparison streamkeeper multi drm create a service access key configure drms for playready widevine and fairplay generate tokens for authorization package and encrypt content for consumer playback test your setup with verimatrix s test player multi drm status codes streamkeeper multi drm status codes client status codes client status codes authorization client status codes cpix client status codes widevine client status codes fairplay client status codes playready token authentication specification system overview security hardening requirements key generation authorization overview drm application specific token authentication widevine claims fairplay claims playready claims cpix claims cpix document encryption cpix query parameters cpix best practices hdcp compatibility drm specific integration apple fairplay streaming certificate setup guide streamkeeper multi drm monitoring watermarking reveal and deepscan reveal service vs deepscan reveal deepscan watermarking frequently asked questions faq cpix service api create content use case live with key rotation use case multi key use case key encryption cpix enhanced security api create content use case signed request vcas monitoring getting started iptv activity dashboard multi drm activity dashboard ott activity dashboard omi activity dashboard supported billing models widevine license request handling streamkeeper multi drm faqs frequently asked questions google widevine content decryption module cdm how the three major drms identify devices verimatrix platform managing users platform user roles multifactor authentication mfa risk detections quick guide setting up sso terms of service for trial use of verimatrix secure delivery platform streamkeeper cpix enhanced security api the cpix v2 0 specification allows for any elements with an id be to signed and verified this feature allows packagers to sign the cpix request as an alternate form of authentication both document signing and key encryption must be supported by packagers in order to remove the requirement for jwt authentication the packager is expected to sign the cpix document so that streamkeeper drm can authenticate the document following the xml signature syntax and processing version 1 1 specification in turn the streamkeeper drm signs the response so that the packager can verify the document for more information refer to key encryption in the cpix document digital signature updated over 1 year ago what s next create content did this page help you yes no copy page www verimatrix com terms of use privacy notice 2025 verimatrix all rights reserved