New and updated Spring Security plugins
Locked
12
12
New and updated Spring Security plugins
 
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Both plugins support event handling. For Acegi see http://grails.org/AcegiSecurity+Plugin+-+Acegi+Events and for the new plugin see Chapter 7 in http://burtbeckwith.github.com/grails-spring-security-core/docs/manual/
Burt > > I'm using the old ACEGI plugin, what would be good in the new LDAP plugin is > to fire a 'org.springframework.context.ApplicationEvent' on successful LDAP > authentication. > > My current usercase with the ACEGI plugin is all users should be in LDAP but > I am required to also have a User model by the ACEGI plugin so I need to > automaticaly create Users in grails if they don't exist but LDAP > authenticates. Listening for a event would make this eaiser to do. > > At the minute I achieve the above with Spring AOP by AfterReturing advice > for the following pointcut 'execution(* > org.springframework.security.providers.ldap.authenticator.BindAuthenticator.authenticate(..))'. > Seems to be working ok and fairly simple so I don't have to update the ACEGI > plugin like some of the sugestions I've seen on this mailing list. > |
signature.asc (205 bytes)
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
No, this isn't supported. You wouldn't edit web.xml though. See section 16 in the docs, http://burtbeckwith.github.com/grails-spring-security-core/docs/manual/
You can either specify the position of a filter using clientRegisterFilter() or explicitly list the ordered filter bean names with 'filterNames'. Spring Security defines all filters as Spring beans and you need to follow that convention - specify the bean name(s) you use in resources.groovy to idenfity them. Burt > > I want to use saml validation with this plugin. Does this supported by this > plugin. > I had to make modifications to plugin to use Saml11TicketValidator and add > then manullay add the Saml11TicketValidationFilter and > HttpServletRequestWrapperFilter web.xml of the app. > > Is that the right approach or its more configurable than this hard coding > directly > |
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
There are PDF docs for all of the plugins except the UI plugin. That one is broken because the images are too wide and they clip, but I'll work on that. If you go to the Github pages there are links to the HTML and PDF versions:
http://burtbeckwith.github.com/grails-spring-security-core/ http://burtbeckwith.github.com/grails-spring-security-openid/ http://burtbeckwith.github.com/grails-spring-security-acl/ http://burtbeckwith.github.com/grails-spring-security-cas/ http://burtbeckwith.github.com/grails-spring-security-ldap/ http://burtbeckwith.github.com/grails-spring-security-ui/ (will have the link when it's fixed) Burt > Hi Burt, can we get the doc in PDF format? > > On Wed, Aug 4, 2010 at 3:04 AM, Burt Beckwith <[hidden email]> wrote: > > > No, this isn't supported. You wouldn't edit web.xml though. See section 16 > > in the docs, > > http://burtbeckwith.github.com/grails-spring-security-core/docs/manual/ > > > > You can either specify the position of a filter using > > clientRegisterFilter() or explicitly list the ordered filter bean names with > > 'filterNames'. Spring Security defines all filters as Spring beans and you > > need to follow that convention - specify the bean name(s) you use in > > resources.groovy to idenfity them. > > > > Burt > > > > > > > > I want to use saml validation with this plugin. Does this supported by > > this > > > plugin. > > > I had to make modifications to plugin to use Saml11TicketValidator and > > add > > > then manullay add the Saml11TicketValidationFilter and > > > HttpServletRequestWrapperFilter web.xml of the app. > > > > > > Is that the right approach or its more configurable than this hard coding > > > directly > > > > > > > > > |
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
I'm working on that, should be available in a few weeks.
Burt > > Is there an oauth module? |
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
Re: New and updated Spring Security plugins
|
|
Re: New and updated Spring Security plugins
|
|
If you could create a small project that demonstrates the issue and create a JIRA issue (run 'grails bug-report' to create the project zip) I'll take a look.
Burt > > Me again, > > I have a small issue using the core spring-security-plugin together with the > datasources plugin. While login works fine if I use as primary DB the one > for User, Role, etc., it does not work anymore if I swap and configure it as > secondary DB via the datasources plugin. (without errors, just a "Sorry, we > were not able to find a user with that username and password."). > > Here the working config: > > // dataSource.groovy > > dataSource { > logSql = true > } > > hibernate { > format_sql=true > cache.use_second_level_cache=true > cache.use_query_cache=true > cache.provider_class='net.sf.ehcache.hibernate.EhCacheProvider' > } > > // environment specific settings > environments { > development { > dataSource { > url = "jdbc:jtds:sybase://myserver.mydomain.org:6789/user_portal" > driverClassName = "net.sourceforge.jtds.jdbc.Driver" > username = "username" > password = "password" > dialect = "org.hibernate.dialect.SybaseDialect" > } > } > } > > and > > datasources = { > datasource(name: 'up_dev') { > environments(['development']) > domainClasses([]) > readOnly(true) > driverClassName('com.mysql.jdbc.Driver') > url('jdbc:mysql:///nightlog') > username('username') > password('password') > logSql(true) > dialect('org.hibernate.dialect.MySQL5Dialect') > hibernate { > cache { > provider_class('net.sf.ehcache.hibernate.EhCacheProvider') > use_second_level_cache(true) > use_query_cache(true) > } > } > } > } > > > And here is the swapped config that does NOT work: > > > // DataSource.groovy > dataSource { > logSql = true > } > > hibernate { > format_sql=true > cache.use_second_level_cache=true > cache.use_query_cache=true > cache.provider_class='net.sf.ehcache.hibernate.EhCacheProvider' > } > > // environment specific settings > environments { > development { > dataSource { > url = "jdbc:mysql:///nightlog" > driverClassName = "com.mysql.jdbc.Driver" > username = "username" > password = "password" > dialect = "org.hibernate.dialect.MySQL5Dialect" > } > } > } > > > > and > > > datasources = { > datasource(name: 'up_dev') { > environments(['development']) > > domainClasses([org.mydomain.User,org.org.mydomain.Role,org.mydomain.UserRole, > org.mydomain.Profile]) > readOnly(true) > driverClassName('net.sourceforge.jtds.jdbc.Driver') > url('jdbc:jtds:sybase://myserver.mydomain.org:6789/user_portal') > username('username') > password('password') > logSql(true) > dialect('org.hibernate.dialect.SybaseDialect') > hibernate { > cache { > provider_class('net.sf.ehcache.hibernate.EhCacheProvider') > use_second_level_cache(true) > use_query_cache(true) > } > } > } > } > > > I do see the query going to the DB properly. > > > Hibernate: > select > user0_.account_id as account1_8_, > user0_.activated as activated8_, > user0_.`passwd` as passwd3_8_, > user0_.username as username8_ > from > accounts user0_ > where > user0_.username=? > > > Also, I noticed that on my domain class the overridden method > > > String getPassword() { > password? password.trim() : "" > } > > > Is no longer called. Did anybody try using the datasources plugin with the > spring security one? > > Thanks > > .t > |
Re: New and updated Spring Security plugins
|
|
| Free forum by Nabble | Edit this page |