I have a Grails application I am developing that uses the Spring Security plugin version 2.0-RC2. My authentication process has been working using spring security for my login page. I just updated from Grails 2.3.2 to 2.3.3 and I am now getting the following error:
Authentication request failed: org.springframework.security.authentication.AuthenticationServiceException: No transactionManager bean configured
Has anyone else seen this when upgrading Grails with spring security?
Did you fix the Hibernate plugin dependency? You need a new version in 2.3.3 - see http://grails.org/2.3.3+Release+Notes
Related
I have been developing a web app using Spring Boot and Spring Security among other things.
Everything was working well till I integrated with JavaMelody. Now, every REST API call annotated with #PreAuthorize is giving a HTTP status 404.
How can I configure JavaMelody for working with Spring Security? I followed the official guide to integrate JavaMelody in a Spring Boot app (https://github.com/javamelody/javamelody/wiki/UserGuideAdvanced#spring-boot-app) and so JavaMelody is working, but... I did not find any info about my situation.
Updated Spring Boot to 1.4.1 and now it is working.
I have a big(multiple custom plugin based) Grails project, which runs perfectly fine on Tomcat server.
Now for a new customer we need to deploy it on JBoss Application server. It seems to deploy fine without any error but when I try to login on the first page which is implemented using Spring Security plugin. It does not log me in. I have tried going to a valid URL to check if its a problem of redirecting but it is not the case.
Please note it is not showing any error on the log. And since it is not properly executable in development environment so each time I need to build a WAR file to test it.
Grails version: 2.4.4
Spring security version: ':spring-security-core:2.0-RC4'
JBoss version: wildfly-9.0.2.Final
I tried some setups, and they all worked as a simple new project.
I used grails 2.4.4 and spring-security 2.0-RC4.
Here are a few things you could try:
Use latest spring-security version 2.0.0
compile "org.grails.plugins:spring-security-core:2.0.0"
Add jboss plugin and generate deployment xmls (this is needed for grails 2.5.4)
build ':jbossas:1.0'
$grails generate-boss-deploy 6
Create a brand new Wildfly install and deploy your app.
I can only think about a infrastructure problem, since I got no problem with the same setup. I running on Mac, with java 8 and Wildfly 9.0.2 final. Tested grails 2.4.4 and 2.5.4, spring security 2.0-RC4 and 2.0.0.
Best,
Eder
I have Spring Boot beased web application using Spring Security 4.0.2 for authentication. My app deployed to WebLogic 12c with configured security realm.
I want to configure Spring Security authorization through WebLogic security realm.
I tried finding in net but unable to get any working and actual samples which explains the Weblogic/Spring-Sec working together.
I need Spring Security java configuration sample for WebLogic security realm.
Can anyone help me with this issue?
I'm trying to upgrade my Spring Boot application with a Spring Security from version 3.2.7.RELEASE to recently released 4.0.0.RELEASE version and now it stopped working with "Access Denied" exception.
Before, I have successfully used Spring Security oAuth2 version 2.0.7.RELEASE and Spring Security 3.2.7.RELEASE
What can be a reason of it ?
If you're trying to use Spring Security 4.0.0 with Spring Security OAuth2, it currently is not officially supported:
https://github.com/spring-projects/spring-security-oauth/issues/452
after updating my grails app's security plugins, i get the following error when deploying to tomcat:
2012-01-17 09:13:04,970 [pool-2-thread-1] ERROR context.ContextLoader - Context initialization failed
org.springframework.beans.factory.access.BootstrapException: Error executing bootstraps; nested exception is org.codehaus.groovy.runtime.InvokerInvocationException: groovy.lang.MissingMethodException: No signature of method: static org.example.SecRole.findByAuthority() is applicable for argument types: (java.lang.String) values: [ROLE_USER]
the app works fine when being tested via run-app.
the SecRole class has been automatically generated by the spring security plugin.
i had previously deployed the app on the same server without a problem when using an older version of the spring security plugin.
have been knocking my head against this for hours. ideas much appreciated.
This is a bug in v1.2.7 of the plugin. I released v1.2.7.1 to fix it; you can also downgrade to v1.2.6.
Are you using your own Spring Security's User and Role class?
Did you tried to create a fresh grails project and install it with vacation request sample app to test it out?
Lastly, may I know which Grails version and OS you use?
Cheers,
Chee Kin
My prod Env: Tomcat 7, Fedora, Grails 1.3.7, activiti-spring-security 0.4.6, spring-security-core 1.2.7 activiti 5.8.2
Dev Env: Mac OS 10.6, Grails 1.3.7, activiti-spring-security 0.4.6, spring-security-core 1.2.7, activiti 5.8.2
I have installed vacation request app on fresh grails project and that works fine when I run using grails run-app (both in dev and prod mode).
As per Peter's comment above, upgrading to Grails 2.0 solved the problem I described above. However, I had subsequently run into a host of upgrade issues with the app.