Use the MDRM page to whitelist Data Plane IP addresses and to upload the FairPlay certificate that serves playback. You can save the IP list and the certificate separately.
You need permission to manage MDRM. If the fields are locked, your role can view the page and cannot change it.
The Whitelist IPs list is the set of Data Plane addresses MDRM accepts. Add every address that should be allowed. Each entry is stored on its own.
Open MDRM
In Whitelist IPs, type an address and press Enter, or choose Add under the field. Use CIDR notation, for example
35.240.51.82/32
Repeat for each additional address.
Choose SAVE
SAVE stays unavailable until the list differs from the saved list.
An address already in the list is ignored, and the page tells you it was ignored.
Remove an address by choosing the remove icon on its chip, then SAVE
When the row is full, extra addresses collapse into a +N chip. Open that chip to see and remove them.
Saving the IP list does not change the FairPlay certificate.
The DRM FairPlay certificate section has two formats:
Format | Label on the page | When to use it |
FairPlay v26 | FairPlay V26 | New setups. This is the current format and has the longer Apple support horizon. |
FairPlay v4 | FairPlay V4, marked LEGACY | Existing v4 deployments, or a specific compatibility need. |
The version that is serving playback is marked ACTIVE. The page opens on that version. The note under the form tells you the state of the version you are viewing:
This version is currently active — serving all playback requests.
Playback uses this certificate.
Configured, not active. Saving will reactivate this version.
The credentials are stored. The next save makes this version the one that serves playback.
Not yet configured. Saving will make this the active version.
The first successful save activates this version.
Saving one version replaces the credentials for that version and makes that version active. The other version’s stored credentials stay in place.
For a new account, open FairPlay V26and configure it there.
If you open FairPlay V4 before any version is configured, the page asks you to confirm. It recommends v26. Choose CONTINUE WITH V4 only if you intend to use the legacy format. You can move to v26 later.
If v26 is already active and you open FairPlay V4, the page warns you that v4 is the legacy format. Choose CANCEL to stay on v26, or CONTINUE to view and edit the v4 credentials.
v26 needs four credentials from Apple SDK 5 or higher. SAVE is available only after all four are filled.
Open
FairPlay V26
FPS Certificate.
Upload a .der, .cer, or .bin file. The value must be valid Base64. After a readable certificate is loaded, the page shows common name, country, organization, organizational unit, valid from, and valid to.
FPS Provisioning Data. Upload the FairPlay provisionData.binfile supplied with Apple SDK 5 or higher.
Private Key (1024-bit).
Upload the 1024-bit .pemfile, or paste the PEM text.
Private Key (2048-bit).
Upload the 2048-bit .pem file, or paste the PEM text.
If a private key file is encrypted, turn on Private key is encrypted for that key and enter private key's Passphrase. An encrypted key cannot be saved without its passphrase. Synamedia uses the passphrase to decrypt the key and does not store the passphrase.
Choose SAVE, then confirm.
To replace an existing v26 certificate, choose EDIT, confirm, replace all four credentials, then SAVE. Saving replaces the previous v26 keys. If v26 is not the active version, that save also makes v26 active.
v4 needs three credentials. SAVE at the bottom of the form is available only after all three are filled.
Open
FairPlay V4. Confirm the legacy warning if it appears.
Application secret key.Enter a 32-character hexadecimal string.
FPS Certificate. Upload a .der, .cer, or .binfile. A readable certificate shows the same certificate details as v26.
FPS Certificate private key.
Upload a .pem file, or paste the PEM text. If the file is encrypted, turn on Private key is encrypted and enter the passphrase. Synamedia does not store the passphrase.
Choose SAVE, then confirm. The confirmation states that saving replaces all previous v4 keys. If v4 is already stored and is not active, the confirmation also states that this save makes v4 the active version.
To change one stored v4 credential, choose EDIT on that field, confirm, update the value, and SAVE that field.
A successful save shows Successfully updated.
The application secret key, provisioning data, and private keys are shown afterward as a hash of the stored value. Copy that hash with the copy icon on the field. The original secret is not shown again.
The FPS certificate text stays on the page, with its certificate details when the file can be read.
Updating the FPS certificate publishes that certificate for playback.
If the save fails, the page shows the error and keeps the previous active version in place.
