sramanna

Hello Sridevi, I am sorry, I wont be able to help you. We are not upgrading from 3.0. I have only tested this feature on 3.0. We are doing a new project on 3.5 Shiv

Thank you so much for your reply ! that helped..

This looks like a bug to me in 3.5. As far as I can see, this type of request handling is done by requestParameterAuthenticationFilter in the filter chain. Though there is a replacement provided for every filter class (for example, basic,authentication, user preferences etc) in the new applicationContext-multiTenancy.xml, the replacement bean is not provided for this filter. It is still using the 3.1 class and hence it looks like it is failing. Can someone please look into this and let me know if this bug will be fixed soon. Also, is there a way I can report a bug ? Thanks Shiv

Hello, On version 3.0, I was able to login passing parameters through URL. For example, http://localhost:6666/jasperserver-pro/flow.html?_flowId=homeFlow&ParentFolderUri=/reports&j_acegi_security_check?&j_username=jasperadmin&j_password=jasperadmin Now, we have upgraded to 3.5, which is multi-tenant. Now the URL based login is not working any more. Please note that I have tried adding orgId as well as a parameter at the end. http://localhost:6666/jasperserver-pro/flow.html?_flowId=homeFlow&ParentFolderUri=/reports&j_acegi_security_check?&j_username=jasperadmin&j_password=jasperadmin&orgId=100 Please let me know what is wrong. Thanks