Skip to main content

Acegi onSuccessfulAuthentication

Some time back, I raised a jira in Acegi, which was turned down. There was no adequate response from spring team. Here I am writing about it, so other spring users (read gurus) may pitch in.
//Edited to short and precise
protected void successfulAuthentication(HttpServletRequest request,
    HttpServletResponse response, Authentication authResult)
    throws IOException {

    SecurityContextHolder.getContext().setAuthentication(authResult);

    String targetUrl = (String) request.getSession()
                 .getAttribute(ACEGI_SECURITY_TARGET_URL_KEY);
    request.getSession().removeAttribute(ACEGI_SECURITY_TARGET_URL_KEY);

    if (alwaysUseDefaultTargetUrl == true) {
        targetUrl = null;
    }

    if (targetUrl == null) {
        targetUrl = request.getContextPath() + defaultTargetUrl;
    }

    // user call back hook
    onSuccessfulAuthentication(request, response, authResult);
    //...
    response.sendRedirect(response.encodeRedirectURL(targetUrl));
}
The Acegi framework's AbstractProcessingFilter provides a callback method onSuccessfulAuthentication for calling user logic after a successful login - generally used for building user login context specific to application. The landing page is *pre-determined* before this call so NO matter what happens in this method, it is redirected to land on the said page. So,  if there is a data or application error while doing it, it is still going to the same page redirected to. The only way to control the flow is by throwing an exception and handling it either by Acegi Exception Handlers or catching that exception in web.xml

My Request was to be able to use a different flow, and send to a different page. In my case, If there was a user that was in our Transaction DB but not in legacy DB, We just come out throw the user an error splash screen. It dint matter much to me. However If you had a business scenario - go to a different controller, build a session different way and send to a different page - How do you do? Have you had this situation? How would you resolve it?

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...