Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for: Click on "manage subscription" causes "invalid signature" #4020

Closed
wants to merge 1 commit into from

Conversation

langemeijer
Copy link
Contributor

This fixes issue: #4013

@vikramarsid
Copy link

@langemeijer I still see the issue, ManageSubscription links cause
Error 403
Invalid signature.
Forbidden

URL is missing signature params

https://example.com/subscribe/manage/mEwLTdnSmkkj2D4FUYhSC8K4sdQY2xUBXwLXjmGLLH

Requires signature:
https://example.com/subscribe/manage/mEwLTdnSmkkj2D4FUYhSC8K4sdQY2xUBXwLXjmGLLH/signature=<signature>

Even after adding the signature, we see the same issue.
This issue is related to #3714

@langemeijer
Copy link
Contributor Author

Please be specific. You now have Cachet generating URLs with a signature? And when visiting this URL, Cachet throws an exception saying that the URL is invalid?

@mattluchterhand
Copy link

mattluchterhand commented Jul 16, 2020

I am experiencing the same issue. When a user first subscribes both the Verify and Manage subscriptions buttons/links function properly. Those links look similar to the following:
https://demo.cachethq.io/subscribe/manage/SUBSCRIBERKEY?signature=SIGNATUREKEY

When the subscriber receives component updates the Unsubscribe link at the bottom works as expected. The Manage Subscription link, however, returns the Error 403 Invalid Signature message. The link looks like this:
https://demo.cachethq.io/subscribe/manage/SUBSCRIBERKEY
I am guessing the issue is the missing ?signature=SIGNATUREKEY

Let me know what other specifics you may need to track down the issue.

@SebastienFourreau
Copy link

HI there !

Can someone merge this?

Thanks

@SebastienFourreau
Copy link

I confirm that this fix works, thanks @langemeijer

@jbrooksuk
Copy link
Member

Thank you for your input on Cachet 2.x. We are shifting our attention and resources to Cachet 3.x and will no longer be supporting the 2.x version. If your feedback or issue is relevant to the 3.x series, we encourage you to engage with the new branch.

For more information on the Cachet rebuild and our plans for 3.x, you can read the announcement here.

We appreciate your understanding and look forward to your contributions to the new version.

@jbrooksuk jbrooksuk closed this Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants