#Problem with Spring Security

14 messages · Page 1 of 1 (latest)

weary plaza
#

Hello, I would be grateful for help
I do the logic that when users were registered immediately and in the keycloak also
were created, so here is the problem encountered that the method /api/v1/users/user, to which I explicitly indicated that permitAll() still requires authorisation, please tell me how to be, thank you in advance.
Here I made another pure get method to test whether permitAll() was applied at all and everything works fine.

neat sandalBOT
#

This post has been reserved for your question.

Hey @weary plaza! Please use /close or the Close Post button above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

grand thorn
neat sandalBOT
#

💤 Post marked as dormant

This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.

weary plaza
grand thorn
#

for users/user

weary plaza
grand thorn
weary plaza
# grand thorn do you have keycloak set up in security config

i solved this problem
In the single chain, I had the resource server (JWT) enabled and CSRF disabled. For an ‘anonymous’ POST, this is a classic 403. In the public chain, we disabled CSRF, so POST /api/v1/users/user started to work.
Thanks for help

neat sandalBOT
grand thorn
#

oh

#

nice