You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been using pusher for years now, with our PHP backend sending events that are consumed by our JS frontend and that works very well.
However we're now implementing a new pusher based solution where the backend is .net and the frontend is the same JS frontend, and we were surprised when the decryption on the frontend failed. After some digging it seems to be caused due to different algorithms being used to generate the shared secret.
It looks like the .net library uses HMAC-SHA256 where as the other side uses simple SHA256, making it incompatible. For now we're forking the .net library to adjust for that, but if possible, consider standardizing the algorithm used across different libraries.
The text was updated successfully, but these errors were encountered:
We've been using pusher for years now, with our PHP backend sending events that are consumed by our JS frontend and that works very well.
However we're now implementing a new pusher based solution where the backend is .net and the frontend is the same JS frontend, and we were surprised when the decryption on the frontend failed. After some digging it seems to be caused due to different algorithms being used to generate the shared secret.
It looks like the .net library uses HMAC-SHA256 where as the other side uses simple SHA256, making it incompatible. For now we're forking the .net library to adjust for that, but if possible, consider standardizing the algorithm used across different libraries.
The text was updated successfully, but these errors were encountered: