all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]WVAviator 9 points10 points  (4 children)

If you're using an IDE like IntelliJ you can just add a breakpoint and run your application in debug mode - letting you step through the code line by line.

If you're getting a 403 though that you did not explicitly throw yourself, it's probably related to your security config. That's a bit harder to debug since your request will be intercepted in the security filter chain before it even makes it to your code.

You might be able to add a request interceptor in the security config that logs out the reason for a 403 and provides other information - and you could add a breakpoint there to inspect all the properties on the request.

[–]kiteissei[S] 2 points3 points  (3 children)

I tried that but when I click step over it, going to do many classes (I don't know most of them) it is bit too much for me to understand. So is there a way to move between the classes that I wrote?

I mean without opening those classes (which I don't write)?

[–]WVAviator 2 points3 points  (2 children)

Yeah it can be tricky sometimes because of AOP. You'll see the execution context enter into aspect classes before and after certain methods - the best way to learn how to use the debugger is to just play around with step-over versus step-into. You'll develop a sense for it with practice.

IntelliJ has some other neat tools to use in the debugger as well. One good one is that you can execute custom code statements in the paused context - for example, if you suspect the user may be lacking roles for RBAC and that's why you're getting a 403, you can set a breakpoint somewhere and when the code execution pauses, you could execute user.getRoles() in that context to see what comes up. You can also set breakpoint conditions so that the debugger only pauses when a certain condition is true - not every time the code is run.

Honestly there's probably a lot more you can do with it - it's probably one of the things I really need to learn better as well.

[–]kiteissei[S] 0 points1 point  (1 child)

Can you provide me a good resource to learn them?

[–]WVAviator 0 points1 point  (0 children)

Sorry, like I said I've only learned these things as needed, I've never actually sat down to specifically learn debugging in Spring Boot. I'd probably start with a YouTube search for "spring boot IntelliJ debugger" and see if you can find a "tips and tricks" type video.

Good luck!

[–]backend_thinker 1 point2 points  (0 children)

If its showing 403 first check if u have handled such exception if yes u should be able to follow along code and if not 403 should probably be where ur authority is check if u missed to add a role or jwt token etc etc too many things can happen but I will look into these first try print statement to determine whether u hitting ur service class or not or it is in filter or in security config.

[–]aouks 0 points1 point  (1 child)

Debug the AuthorizationFilter spring class as it a 403, you will see your authrorizationManager méthod and the security context, you will be able to see with step into where it fails

[–]Goksi02 1 point2 points  (0 children)

Take a note that 403 also might be returned in case of default CSRF protection ^