werpu

Thanks a lot this is indeed the issue... I will stop investigating it and will wait for the next release...

Additional info. As it seems to me something still triggers into db, although the full authorization does not come from it anymore, it already comes from the InMemoryDaoImpl. I am a little bit puzzled on this, is there something in the jasper server itself which blocks the forwarding if the user cannot be found in the db itself?

Hello. I am trying to switch auth mechanisms from the db based dao to the predefined in memory dao impl. I have defined my own in memory dao impl via a spring framework entry: <bean id="inMemoryDaoImpl" class="org.acegisecurity.userdetails.memory.InMemoryDaoImpl"> <property name="userMap"> <value> jasperadmin=newPassword,ROLE_USER,ROLE_ANONYMOUS,ROLE_ADMINISTRATOR user1=user1password,ROLE_USER,ROLE_ANONYMOUS,ROLE_ADMINISTRATOR test=test,ROLE_USER,ROLE_ANONYMOUS </value> </property> </bean> and have assgined the dao impl to the proper authenticationprovider setting: <bean id="daoAuthenticationProvider" class="org.acegisecurity.providers.dao.DaoAuthenticationProvider"> <!-- jdbcDaoImpl --> <!-- <property name="userDetailsService"><ref bean="inMemoryDaoImpl"/></property> --> <property name="userDetailsService"><ref bean="userAuthorityService"/></property> <!-- <property name="passwordEncoder"><ref local="passwordEncoder"/></property> --> </bean> Now what happens ins following, the jasper server now authenticates the users defined by the inMemoryDaoImpl and lets them pass. Strangely it adds the users to its own database and after adding it, it does not reroute to the main page or allows to access the main page. The user however is authenticated but something within the jasper server seems to still block. The funny thing is, once I move the dao impl reference back to the userAuthorityService the new users which have been added to the datase start to work. Am I missing something here, which is essential? Thanks for your help, Werner Punz