# \[DRM\] \[FairPlay\] skd (and EXT-X-KEY altogether) missing from HLS manifest

**URL:** <https://community.bitmovin.com/t/drm-fairplay-skd-and-ext-x-key-altogether-missing-from-hls-manifest/3165>\
**Category:** Support\
**Tags:** drm, fairplay\
**Created:** [July 31, 2024, 9:06am UTC](https://community.bitmovin.com/t/drm-fairplay-skd-and-ext-x-key-altogether-missing-from-hls-manifest/3165 "2024-07-31T09:06:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lukasz.Bajorski](https://avatars.discourse-cdn.com/v4/letter/l/91b2a8/32.png) [@Lukasz.Bajorski](https://community.bitmovin.com/u/Lukasz.Bajorski)\
**Post date:** [July 31, 2024, 9:06am UTC](https://community.bitmovin.com/t/drm-fairplay-skd-and-ext-x-key-altogether-missing-from-hls-manifest/3165/1 "2024-07-31T09:06:19Z")

</div>

### Product

Encoding - VOD

### Question

Hello folks,

When encoding with DRM protection, I provide the IV and URI in FairPlay Cenc config, however it’s not included in the resulting HLS manifest (no skd and no EXT-X-KEY element). Do you know if there is configuration I need to tweak to be able to add this to the manifest? Or perhaps a second DRM config / manifest needs to be made for FairPlay-only?

Cheers,  
Łukasz

---

<div class="post-metadata">

**Author:** ![albertobitmovin](https://sea1.discourse-cdn.com/flex015/user_avatar/community.bitmovin.com/albertobitmovin/32/256_2.png) [@albertobitmovin](https://community.bitmovin.com/u/albertobitmovin)\
**Post date:** [August 6, 2024, 9:23am UTC](https://community.bitmovin.com/t/drm-fairplay-skd-and-ext-x-key-altogether-missing-from-hls-manifest/3165/2 "2024-08-06T09:23:22Z")

</div>

Hi @Lukasz.Bajorski ,

Thanks for asking in the Community. To confirm, are you creating the DRM config via this endpoint? [Add CENC DRM to an fMP4 muxing](https://developer.bitmovin.com/encoding/reference/postencodingencodingsmuxingsfmp4drmcencbyencodingidandmuxingid)

I assume you also get the same results when trying these alternative endpoints?

- [Add FairPlay DRM to an fMP4 muxing](https://developer.bitmovin.com/encoding/reference/postencodingencodingsmuxingsfmp4drmfairplaybyencodingidandmuxingid)
- [Add FairPlay DRM to a TS muxing](https://developer.bitmovin.com/encoding/reference/postencodingencodingsmuxingstsdrmfairplaybyencodingidandmuxingid)

If so, I suspect the generated DRM\_ID is not getting correctly assigned to the Manifest variants. Are you creating a Default or a Custom manifest? [Default vs custom manifests](https://developer.bitmovin.com/encoding/docs/default-vs-custom-manifest)

Note that when using the custom manifest approach, you can manually assign the drmId to each component, which should resolve the issue:

- [https://developer.bitmovin.com/encoding/reference/postencodingmanifestshlsstreamsbymanifestid](https://developer.bitmovin.com/encoding/reference/postencodingmanifestshlsstreamsbymanifestid)
- [https://developer.bitmovin.com/encoding/reference/postencodingmanifestshlsmediavideobymanifestid](https://developer.bitmovin.com/encoding/reference/postencodingmanifestshlsmediavideobymanifestid)
- [Add Audio Media](https://developer.bitmovin.com/encoding/reference/postencodingmanifestshlsmediaaudiobymanifestid)

If the above doesn’t help, could you share the affected encodingID and manifestID so we can review?

Thank you!

---

<div class="post-metadata">

**Author:** ![Lukasz.Bajorski](https://avatars.discourse-cdn.com/v4/letter/l/91b2a8/32.png) [@Lukasz.Bajorski](https://community.bitmovin.com/u/Lukasz.Bajorski)\
**Post date:** [August 6, 2024, 11:06am UTC](https://community.bitmovin.com/t/drm-fairplay-skd-and-ext-x-key-altogether-missing-from-hls-manifest/3165/3 "2024-08-06T11:06:49Z")

</div>

Hi @albertobitmovin,

Thanks a lot for your answer.

We were aiming at max simplicity to start with, so we were only trying CencDrm and default manifests.

I’ll look into the specific fairplay drm and potentially non-default manifests, perhaps that will indeed solve the issue. If not, I’ll get back to you 🙂

Cheers,  
Łukasz