After (pointlessly) having tweaked/fiddled with CCDL to make it work on the Yanmaga/YoungAnimal/Youngchampion viewer I noticed that YoungChampion updated how they do the authorization.
Rather than putting the User JWT token in the request itself, it is now using a normal user-id and the JWT token moved to the request header in the form of an authorization token.
Chrome plugins are a bit outside of my wheelhouse or I'd make a PR myself, but specifically for YoungChampion (and I assume they'll roll out this fix to the other two sites later), points-unlocked albums need the JWT Auth token grabbed from the contentsinfo request header and re-used.
After (pointlessly) having tweaked/fiddled with CCDL to make it work on the Yanmaga/YoungAnimal/Youngchampion viewer I noticed that YoungChampion updated how they do the authorization.
Rather than putting the User JWT token in the request itself, it is now using a normal user-id and the JWT token moved to the request header in the form of an authorization token.
Chrome plugins are a bit outside of my wheelhouse or I'd make a PR myself, but specifically for YoungChampion (and I assume they'll roll out this fix to the other two sites later), points-unlocked albums need the JWT Auth token grabbed from the contentsinfo request header and re-used.