| Expand | ||
|---|---|---|
| ||
|
...
To load HTTP or HTTPS content, BrightSign players must be able to add the certificates that correspond to that content. You can add this ability through BrightAuthor, BrightAuthor:connected, or through scripts used by BrightAuthor:connected. BrightSign partners who write their own CMS solutions must add the ability to manage certificates.
...
Users can install an unsigned certificate package through roKeystore (or keystore), AddClientCertificate or AddCACertificate, before accessing the resource.
The roKeystore (or keystore) objects allow users to register client certificates with the player. In roKeystore, use AddCAPackage to install persistent .bsca packages.
A .bsca is required if the client is using an HTTPS URL with a certificate signed by a non-public root or intermediate for recovery, because there’s no way to add the certificate before the recovery URL is accessed. This is also true when an HTTPS proxy is used and that proxy uses internal/self-signed certificates. HTTPS URLs using certificates the player already trusts are okay, as long as the player’s clock is set so certificate selection can happen.
...