New members using Okta can load /new then get Forbidden on publish. email_verified is true. The guidelines modal was accepted.
Is there another gate on assert_can_post we should look at? Logs show role=member and trust level 0 for the first hour.
We are not hitting the new-user topics-per-day cap — this is the first post.
Here is the approach that worked on our tenant:
topic_type stored is the canonical id (question, not support).topic:detail:v4:{slug} in Valkey if the HTML looks stale.acceptedAnswer after a hard reload.That unblocked Why does SSO login succeed but the first POST return 403? for us. If it still 403s, look at assert_can_post.
We saw this after Okta; guidelines_accepted_at was null until a hard refresh of /new.
This worked. Marking as accepted so the next search hits a solved Question.
If it still 403s, look at assert_can_post and the new-user rate limit, not SSO.
Thanks — leaving this up for the next team that searches the same string.
New members using Okta can load /new then get Forbidden on publish. email_verified is true. The guidelines modal was accepted.
Is there another gate on assert_can_post we should look at? Logs show role=member and trust level 0 for the first hour.
We are not hitting the new-user topics-per-day cap — this is the first post.
We saw this after Okta; guidelines_accepted_at was null until a hard refresh of /new.
This worked. Marking as accepted so the next search hits a solved Question.
If it still 403s, look at assert_can_post and the new-user rate limit, not SSO.
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
Here is the approach that worked on our tenant:
topic_typestored is the canonical id (question, notsupport).topic:detail:v4:{slug}in Valkey if the HTML looks stale.acceptedAnswerafter a hard reload.That unblocked Why does SSO login succeed but the first POST return 403? for us. If it still 403s, look at
assert_can_post.