CODEWITHSUNDEEP
springmethodscontrolleruserinfo
dumb_terminal
dumb_terminal

Reputation: 1825

Spring calling controller method based on user information

Suppose there are two type of roles in the application -

  1. Admin
  2. Zonal Manager

Admins can get all the office ids while the zonal managers can get only the office assigned under his zone. In the controller I want something like this

@RequestMapping(method = RequestMethod.GET)
Collection<Long> getOfficeIds(){
    // returns all office ids in system
}

@RequestMapping(method = RequestMethod.GET, value = "/{zoneId}")
Collection<Long> getOfficeIds(@RequestParam("zoneId") long zoneId){
    // returns all office ids in the zone
}

Now I want all my users to make request with the no-arg version only (the first method). The system should get user role before hitting controller and should call appropriate controller method (if admin then call the first method, if zonal manager call the second one with appropriate zone).

The question is , is it possible at all ? If yes then what would be the best way of doing this ? I could try to modify the request in a servlet filter. Is there a way using method argument resolver ?

Upvotes: 0

Views: 1428

Answers (1)

Andonaeus
Andonaeus

Reputation: 872

Per comments, I am posting the answer below.

The best thing to do to achieve your goal is to add a filter which runs before the request is handled by the controller. In this filter, you can apply the appropriate logic to determine the requesting user's role and act accordingly. If you follow the same URL pattern in all of your controllers to handle these different cases, you can simply rewrite the internal URL after determining which case to apply so that it can be handled by the appropriate controller. In this way, you can keep all of your user-role logic in one location and your controller logic can handle their own, separate flows accordingly.

To create such a filter using spring, you may do something like the following:

@Component("accountContextFilter") public class AccountContextFilter extends OncePerRequestFilter { 

    public void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws ServletException, IOException{
        //user role and routing logic
    }
}

The reference for the logic inside doFilterInternal can be found here: How to use a servlet filter in Java to change an incoming servlet request url?

Simply change the request path accordingly by appending to your route with the role-defined URLs and you're done.

Upvotes: 1

Related Questions