Our new Community environment is going to be launched soon!
This means that you will be redirected to the new environment automatically, where you can sign-in, look up - and post topics again. Please note that not all topics will be transferred, so it might occur that you can’t find the topic you were looking for.
When you load a "get" or "post" endpoint, as a page inside Betty Blocks and the Authentication Profile is set to "Internal Betty Blocks account (Internal Betty Blocks authentication)", you get an "Authentication is required but we cannot authorize this request" error in the log.
This is not so much an issue when you load a "get" endpoint; the endpoint is shown as normal. But when the Authentication Profile is set to "Internal Betty Blocks account (Internal Betty Blocks authentication)" on a "post" endpoint, you get the same error in the log and the assigned action is not being executed and a blank screen is shown. (The blank screen might be obvious because the redirect event in de action is also not executed.) At this stage, csrf is disabled.
The "Authentication is required but we cannot authorize this request" error is the only thing shown in the log. Something funny about the REQUEST info is the logoutRequest:
Can someone please help me out here?
BTW: I also experience this at endpoints that were working just fine previously.
Hey,
When you load a "get" or "post" endpoint, as a page inside Betty Blocks and the Authentication Profile is set to "Internal Betty Blocks account (Internal Betty Blocks authentication)", you get an "Authentication is required but we cannot authorize this request" error in the log.
This is not so much an issue when you load a "get" endpoint; the endpoint is shown as normal. But when the Authentication Profile is set to "Internal Betty Blocks account (Internal Betty Blocks authentication)" on a "post" endpoint, you get the same error in the log and the assigned action is not being executed and a blank screen is shown. (The blank screen might be obvious because the redirect event in de action is also not executed.) At this stage, csrf is disabled.
The "Authentication is required but we cannot authorize this request" error is the only thing shown in the log. Something funny about the REQUEST info is the logoutRequest:
Can someone please help me out here?
BTW: I also experience this at endpoints that were working just fine previously.
Login to replyI've tried to reproduce this issue but I can't seem to make this happen. If it it is still an issue, please contact us through Intercom.