Custom authorization - 0.8.2 to 0.9 upgrade woes

[karldmoore]

If you put your code in [ code] [ /code] tags, it's sooooo much easier to read. You now need to extend JdbcDaoImpl and override the initMappingSqlQueries method.

    /**
     * Extension point to allow other MappingSqlQuery objects to be substituted in a subclass
     */
    protected void initMappingSqlQueries() {
        this.usersByUsernameMapping = new UsersByUsernameMapping(getDataSource());
        this.authoritiesByUsernameMapping = new AuthoritiesByUsernameMapping(getDataSource());
    }

[sazzadul]

If you put your code in [ code] [ /code] tags, it's sooooo much easier to read. You now need to extend JdbcDaoImpl and override the initMappingSqlQueries method.

    /**
     * Extension point to allow other MappingSqlQuery objects to be substituted in a subclass
     */
    protected void initMappingSqlQueries() {
        this.usersByUsernameMapping = new UsersByUsernameMapping(getDataSource());
        this.authoritiesByUsernameMapping = new AuthoritiesByUsernameMapping(getDataSource());
    }

Now I am one step ahead, everything is working fine now except one thing that is when I log in with correct username and password I get the following error message:

 
Reason: SQL 'SELECT LoginName, UserPassword, Email, FirstName, LastName FROM Users WHERE LoginName=?' requires 1 bind variables, but 0 variables were declared for this object; nested exception is org.springframework.dao.InvalidDataAccessApiUsageException: SQL 'SELECT LoginName, UserPassword, Email, FirstName, LastName FROM Users WHERE LoginName=?' requires 1 bind variables, but 0 variables were declared for this object

[karldmoore]

There must be a problem with the query class. Is it possible to have a look at it?

[sazzadul]

There must be a problem with the query class. Is it possible to have a look at it?

Now I have found out what the problem was, I left out following lines from the constructor

declareParameter(new SqlParameter(Types.VARCHAR));
compile();

Thank you very very much for your help, I really appreciate it.

[karldmoore]

Not a problem, glad it's all working! By the sounds of it, apart from the JdbcDaoImpl changes, it wasn't that much of a problem.

[Luke Taylor]

You are trying to set the query objects on the JdbcDaoImpl, which only has setters for the sql. Look at the code:

http://monkeymachine.co.uk/acegisecu...bcDaoImpl.html

Use the approach Karl described above (extending JdbcDaoImpl).

[karldmoore]

I'd be interested to know how you found the upgrade process. There were obviously a couple of hiccups but apart from those, how did it go?

[sazzadul]

I'd be interested to know how you found the upgrade process. There were obviously a couple of hiccups but apart from those, how did it go?

I didn't actually upgrade, it was my first attempt getting acegi to work since we are considering using it in our business application. I found most of the documentations on the net and I got help from you when it came to jdbcdaoimpl.

[karldmoore]

Ok, my mistake. I read the original title of the thread and thought you were also doing an upgrade.

[sazzadul]

Ok, my mistake. I read the original title of the thread and thought you were also doing an upgrade.

I would like to use my acegi webapplication as authentication and authorization module for several webapps also a common webapp for security but the problem is with request uri. My acegi webapp has to know which appliacation the request comes from( one way to do this is to have request parameter like &product=netbank ) so that it can redirect again after successful login. The problem is when I use {pageContext.request.contextPath} it gives me context path of acegi webapp not the one the request originally come from. Do you have a suggestion how to get around this ?