Q: how to wrap all client to server calls to add an auth token?

Smart GWT Technical Q&A
1

I am using SmartGWT 2.5 Pro version.

I store an auth token on the client side that is provided by a login service. For now, I am setting this as a browser cookie on the client side using:

  RPCManager rpc = new RPCManager(request, response);
  Cookie[] cookies = request.getCookies();

so all of my RPC service implementations can verify user login, auth, roles, etc.

This is inefficient, right?, and I would prefer to have a universal wrapper on the client side that adds the auth token to every RPC call. Any suggestions for how to do this?

2

Not sure what inefficiency you perceive, but another way to do this is to call the client-side RPCManager.setActionURL() API to add a per-user HTTP parameter to the URL used for all RPC calls. This considered more secure than cookies, as it indicates that the request actually came from a specific page, not just from a browser than has the cookie.