-
Notifications
You must be signed in to change notification settings - Fork 14
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
Token is removed when URL rewriter is applied #19
Comments
Hi @leroyvandijk ,
I'll ask within the team if anyone has some idea's on how to solve your problem or at least provide a workaround. |
@leroyvandijk Any updates on this, we need the info to be able to look into your issue? |
What version of Content are you using, SaaS or PaaS, and if PaaS what version? PaaS, 15.2.3 I've created a workaround that picks up the token from the Authorization header en put that as a query param in the redirect |
Ok thanks @leroyvandijk , I'll discuss it with someone internal that has the knowledge on how the url rewriting works in the backend for the experience manager preview and get back to you. |
Hi Bloomreach team,
We use the URL rewriter to rewrite articles for our website from example /articles/2023/06/other-test to /articles/other-test.
Now when in the experience manager, I want to go to the live preview it first shows me the page:
http://localhost:3000/articles/2023/06/other-test?token=THEWHOLEJWTTOKEN&endpoint=http://localhost:8080/site/resourceapi which gives a 301 and redirects me to this page: http://localhost:3000/articles/other-test?endpoint=http%3A%2F%2Flocalhost%3A8080%2Fsite%2Fresourceapi
As you can see the token is stripped away, which causes the user not to see the edit buttons on the preview page.
Since there is an issue with the experience manager not giving the correct url, the user can edit the pages only through Content -> Documents -> Articles -> Test Article and then the View -> Website button. We currently do not have a solution to fix this, so we thought maybe the frontend app can be adjusted so it actually can pass the token.
I've tested the issue with changing the 'authorizationQueryParameter' in the configuration to something like 'blabla'. Then the token is NOT stripped away anymore, but of course the preview doesn't work anymore.
Is there a way so we can pass the token after the redirect?
Kind regards,
Leroy
The text was updated successfully, but these errors were encountered: