Issue with FairPlay Streaming Certificate SDK 26.x

Question

sps_cl OP

Created Nov ’25

Replies 1

Boosts 0

Participants 2

Hi,

I'm trying to create a FairPlay Streaming Certificate for the SDK 26.x version.

Worth to mention that we already have 2 (1024 and 2048) and we only have the possibility to use our previous 1024-bit certificate (which we do not want because we want a 2048 cert)

Our main issue is that when I upload a new "CSR" file, the "Continue" button is still on "gray" and cannot move forward on the process.

The CSR file has been created with this command:

openssl req -out csr_2048.csr -new -newkey rsa:2048
-keyout priv_key_2048.pem
-subj /CN=SubjectName/OU=OrganizationalUnit/O=Organization/C=US

Some help will be appreciated. Thanks in advance

Best,

Boost

Answer 1

iep OP

2w

You're generating a bundle, it will only generate a complete bundle. It expects both 1024-bit and 2048-bit CSRs. The SDK also expects a certificate bundle to work properly.

The SDK will use the 2048-bit certificate whenever possible; however the 1024-bit certificate is still needed to support legacy devices.

By the way, your FPS certificate's key size is not really as important as you might think. It mostly serves to identify your server as a FPS content provider. The content stays secure as long as you keep your provisioning_data file (or previously, your ASk) secure.

0