JWT malformed error on payments/alpha

[dxphilo]

[dxphilo]

Also noticed when opening premium posts in Safari.

[tess3]

safari desktop, not logged in while trying to access premium posts

[ashutosh1206]

@tess3 @developerphilo can you check if the face the same issue on blogchain.app instead of payments.capsule.social?

[ashutosh1206]

From what I understood, this is an issue only specific to payments.capsule.social and alpha.capsule.social because these are protected by basic authorisation. The username/password is sent in Basic authorisation header, we also use the same header for sending our JWT. I think this is why we see those "jwt malformed" error from capsule-server. I was able to trigger the same error on Chrome as well today

[chrispanag]

was searching this a lot today. On thing we could do is just change the header we use to get the auth token. imo apart from keeping it away from the "standard" there's no actual difference if we use for example the: X-Authorization or X-Access-Token header for our auth.

Unfortunately though we can't change the basic authentication header.