Meta tags:
description=Verimatrix requires that tokens being received are signed using a private key. The message is verified against the public part of this key. Where possible, signers should generate and use their own keys within a trusted environment. Verimatrix will NEVER ask for the private part of the key. OpenSSL…;

Headings (most frequently used words):

key, generation, streamkeeper, multi, drm, faqs, verimatrix, platform, openssl, to, generate, pair, of, ecdsa,

Text of the page (most frequently used words):
key (18), app (14), your (13), the (11), verimatrix (10), for (10), use (9), and (9), #streamkeeper (9), drm (9), multi (8), status (8), codes (8), counterspy (8), dashboard (7), cpix (7), generation (6), client (6), ios (6), generate (5), widevine (5), content (5), android (5), authorization (4), security (4), openssl (4), pair (4), pem (4), authentication (4), service (4), activity (4), case (4), api (4), with (4), fairplay (4), claims (4), page (3), overview (3), tokens (3), signed (3), token (3), platform (3), getting (3), started (3), create (3), deepscan (3), reveal (3), integration (3), playready (3), test (3), data (3), protection (3), signing (3), guides (3), all (2), privacy (2), terms (2), com (2), this (2), you (2), hardening (2), requirements (2), out (2), public (2), using (2), 256 (2), curve (2), ecdsa (2), that (2), private (2), part (2), specification (2), guide (2), managing (2), drms (2), frequently (2), asked (2), questions (2), faqs (2), request (2), supported (2), monitoring (2), encryption (2), watermarking (2), faq (2), certificate (2), setup (2), specific (2), view (2), troubleshooting (2), protecting (2), preparing (2), talk (2), markdown (2), 2025, rights, reserved, notice, www, copy, did, help, yes, updated, over, year, ago, ecparam, genkey, name, prime256v1, noout, ec256, pubout, outform, utility, prime, sha, hash, algorithm, enter, following, commands, recommends, es256, elliptic, digital, signature, algorithms, sign, requires, being, received, are, message, verified, against, where, possible, signers, should, their, own, keys, within, trusted, environment, will, never, ask, 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, enhanced, live, rotation, apple, streaming, hdcp, compatibility, best, practices, query, parameters, document, application, system, player, package, encrypt, consumer, playback, configure, access, tiers, comparison, email, alerting, usage, description, retention, information, 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, endpoints, openapi, append, any, documentation, url, get, its, version,

Text of the page (random words):
key generation 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 append md to any documentation page url to get its markdown version jump to content home guides talk to us guides search talk to us guides key generation key generation 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 streamkeeper multi drm token authentication specification key generation verimatrix requires that tokens being received are signed using a private key the message is verified against the public part of this key where possible signers should generate and use their own keys within a trusted environment verimatrix will never ask for the private part of the key openssl key generation verimatrix recommends that you use es256 elliptic curve digital signature algorithms ecdsa to generate the key pair to sign your tokens to generate a key pair of ecdsa use the openssl utility to generate a key pair using the prime 256 curve and the sha 256 hash algorithm enter the following commands openssl ecparam genkey name prime256v1 noout out ec256 key pair pem openssl ec in key pem pubout out public pem outform pem updated over 1 year ago security hardening requirements authorization overview did this page help you yes no copy page www verimatrix com terms of use privacy notice 2025 verimatrix all rights reserved