ANN: Acegi Plugin 0.3 released

[Tsuyoshi Yamamoto]

The Grails Acegi plugin team is pleased to announce the release of version
0.3 of the plugin.

The Acegi plugin simplifies the work involved in integrating Acegi Security
into Grails applications. By combining a core configuration with
user-specified options and overrides, it creates a best-practice
configuration of Spring Security in any Grails application while allowing
developers to make config changes without having to deal with the complexity
of using Spring Security directly.

This release includes significant enhancements, including:
 - upgrade to Spring Security 2.0
 - new support for LDAP/ActiveDirectory logins, including the option to store
roles in the database, infer them from LDAP group membership, or both
 - new support for OpenID logins that integrate with your application's domain
Users and Roles
 - made more of the configuration user-configurable, e.g. filter, logout
handler, and role voter lists are now configurable - you can easily add your
own, remove existing, or change the order
 - new configuration attributes were added, including mail server port and
mail server JavaMailProperties to allow more control over mail sending and to
allow usage of GMail SMTP
 - GrailsUser is now an interface, and GrailsDaoImpl was reworked to make
subclassing or replacement easier to allow custom database user loading
 - added full suite of unit and integration tests, and also automated
functional tests using WebTest
 - new wrapper for Acegi events that calls optional application-defined
closures when events fire
 - moved all classes to packages
 - enhanced Ajax login support including a brief tutorial
 - lots of updates to the documentation
(http://grails.org/AcegiSecurity+Plugin)
 - bug fix - bypassed DigestUtils for password encryption to allow use of any
supported codec

The plugin and source code are available for download here:

 http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/

For more information on the Grails Acegi plugin, visit the Grails wiki page:

  http://grails.org/AcegiSecurity+Plugin

Feedback, suggestions for improvement and contributions are always welcome.


Cheers!
----------------
The Grails Acegi plugin team

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Edderd]

Thanks for all your hard work guys!

Ed

On Wed, Apr 30, 2008 at 7:37 AM, Tsuyoshi Yamamoto <mottsnite@...> wrote:

The Grails Acegi plugin team is pleased to announce the release of version
0.3 of the plugin.

The Acegi plugin simplifies the work involved in integrating Acegi Security
into Grails applications. By combining a core configuration with
user-specified options and overrides, it creates a best-practice
configuration of Spring Security in any Grails application while allowing
developers to make config changes without having to deal with the complexity
of using Spring Security directly.

This release includes significant enhancements, including:
 - upgrade to Spring Security 2.0
 - new support for LDAP/ActiveDirectory logins, including the option to store
roles in the database, infer them from LDAP group membership, or both
 - new support for OpenID logins that integrate with your application's domain
Users and Roles
 - made more of the configuration user-configurable, e.g. filter, logout
handler, and role voter lists are now configurable - you can easily add your
own, remove existing, or change the order
 - new configuration attributes were added, including mail server port and
mail server JavaMailProperties to allow more control over mail sending and to
allow usage of GMail SMTP
 - GrailsUser is now an interface, and GrailsDaoImpl was reworked to make
subclassing or replacement easier to allow custom database user loading
 - added full suite of unit and integration tests, and also automated
functional tests using WebTest
 - new wrapper for Acegi events that calls optional application-defined
closures when events fire
 - moved all classes to packages
 - enhanced Ajax login support including a brief tutorial
 - lots of updates to the documentation
(http://grails.org/AcegiSecurity+Plugin)
 - bug fix - bypassed DigestUtils for password encryption to allow use of any
supported codec

The plugin and source code are available for download here:

 http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/

For more information on the Grails Acegi plugin, visit the Grails wiki page:

 http://grails.org/AcegiSecurity+Plugin

Feedback, suggestions for improvement and contributions are always welcome.


Cheers!
----------------
The Grails Acegi plugin team

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

--
Ed

[rjain7]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanks for the great job with the plugin !

One question I couldn't answer from the documentation: what is the minimum rev of grails needed to run acegi plugin 0.3 ? I see that you have used grails 1.0.2 in the examples. Will grails 1.0.1 or earlier releases work with it as well ?

-Rahul

----- Original Message ----
From: Tsuyoshi Yamamoto <mottsnite@...>
To: user@...
Sent: Wednesday, April 30, 2008 6:37:08 AM
Subject: [grails-user] ANN: Acegi Plugin 0.3 released

The Grails Acegi plugin team is pleased to announce the release of version
0.3 of the plugin.

The Acegi plugin simplifies the work involved in integrating Acegi Security
into Grails applications. By combining a core configuration with
user-specified options and overrides, it creates a best-practice
configuration of Spring Security in any Grails application while allowing
developers to make config changes without having to deal with the complexity
of using Spring Security directly.

This release includes significant enhancements, including:
- upgrade to Spring Security 2.0
- new support for LDAP/ActiveDirectory logins, including the option to store
roles in the database, infer them from LDAP group membership, or both
- new support for OpenID logins that integrate with your application's domain
Users and Roles
- made more of the configuration user-configurable, e.g. filter, logout
handler, and role voter lists are now configurable - you can easily add your
own, remove existing, or change the order
- new configuration attributes were added, including mail server port and
mail server JavaMailProperties to allow more control over mail sending and to
allow usage of GMail SMTP
- GrailsUser is now an interface, and GrailsDaoImpl was reworked to make
subclassing or replacement easier to allow custom database user loading
- added full suite of unit and integration tests, and also automated
functional tests using WebTest
- new wrapper for Acegi events that calls optional application-defined
closures when events fire
- moved all classes to packages
- enhanced Ajax login support including a brief tutorial
- lots of updates to the documentation
(http://grails.org/AcegiSecurity+Plugin)
- bug fix - bypassed DigestUtils for password encryption to allow use of any
supported codec

The plugin and source code are available for download here:

http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/

For more information on the Grails Acegi plugin, visit the Grails wiki page:

  http://grails.org/AcegiSecurity+Plugin

Feedback, suggestions for improvement and contributions are always welcome.


Cheers!
----------------
The Grails Acegi plugin team

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[burtbeckwith]

I don't know of any issues with 1.0.1 wrt the Acegi plugin.

Burt

On Wednesday 30 April 2008 7:12:29 pm Rahul Jain wrote:

> Thanks for the great job with the plugin !
>
> One question I couldn't answer from the documentation: what is the minimum
> rev of grails needed to run acegi plugin 0.3 ? I see that you have used
> grails 1.0.2 in the examples. Will grails 1.0.1 or earlier releases work
> with it as well ?
>
> -Rahul
>
>
> ----- Original Message ----
> From: Tsuyoshi Yamamoto <mottsnite@...>
> To: user@...
> Sent: Wednesday, April 30, 2008 6:37:08 AM
> Subject: [grails-user] ANN: Acegi Plugin 0.3 released
>
> The Grails Acegi plugin team is pleased to announce the release of version
> 0.3 of the plugin.
>
> The Acegi plugin simplifies the work involved in integrating Acegi Security
> into Grails applications. By combining a core configuration with
> user-specified options and overrides, it creates a best-practice
> configuration of Spring Security in any Grails application while allowing
> developers to make config changes without having to deal with the
> complexity of using Spring Security directly.
>
> This release includes significant enhancements, including:
> - upgrade to Spring Security 2.0
> - new support for LDAP/ActiveDirectory logins, including the option to
> store roles in the database, infer them from LDAP group membership, or both
> - new support for OpenID logins that integrate with your application's
> domain Users and Roles
> - made more of the configuration user-configurable, e.g. filter, logout
> handler, and role voter lists are now configurable - you can easily add
> your own, remove existing, or change the order
> - new configuration attributes were added, including mail server port and
> mail server JavaMailProperties to allow more control over mail sending and
> to allow usage of GMail SMTP
> - GrailsUser is now an interface, and GrailsDaoImpl was reworked to make
> subclassing or replacement easier to allow custom database user loading
> - added full suite of unit and integration tests, and also automated
> functional tests using WebTest
> - new wrapper for Acegi events that calls optional application-defined
> closures when events fire
> - moved all classes to packages
> - enhanced Ajax login support including a brief tutorial
> - lots of updates to the documentation
> (http://grails.org/AcegiSecurity+Plugin)
> - bug fix - bypassed DigestUtils for password encryption to allow use of
> any supported codec
>
> The plugin and source code are available for download here:
>
> http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/
>
> For more information on the Grails Acegi plugin, visit the Grails wiki
> page:
>
>   http://grails.org/AcegiSecurity+Plugin
>
> Feedback, suggestions for improvement and contributions are always welcome.
>
>
> Cheers!
> ----------------
> The Grails Acegi plugin team
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Peter Cold]

Hi Burt-
It sounds like there is not a real smooth upgrade path from 0.2 due to the drastic improvements that have been made here.  Am I way off base on that?  I'd like to get on the latest rev with spring security 2.0, but don't know if I have time to work through the implementation again at this time...

-Peter

On Wed, Apr 30, 2008 at 4:59 PM, Burt Beckwith <burt@...> wrote:

I don't know of any issues with 1.0.1 wrt the Acegi plugin.

Burt

On Wednesday 30 April 2008 7:12:29 pm Rahul Jain wrote:
> Thanks for the great job with the plugin !
>
> One question I couldn't answer from the documentation: what is the minimum
> rev of grails needed to run acegi plugin 0.3 ? I see that you have used
> grails 1.0.2 in the examples. Will grails 1.0.1 or earlier releases work
> with it as well ?
>
> -Rahul
>
>
> ----- Original Message ----
> From: Tsuyoshi Yamamoto <mottsnite@...>
> To: user@...
> Sent: Wednesday, April 30, 2008 6:37:08 AM
> Subject: [grails-user] ANN: Acegi Plugin 0.3 released
>
> The Grails Acegi plugin team is pleased to announce the release of version
> 0.3 of the plugin.
>
> The Acegi plugin simplifies the work involved in integrating Acegi Security
> into Grails applications. By combining a core configuration with
> user-specified options and overrides, it creates a best-practice
> configuration of Spring Security in any Grails application while allowing
> developers to make config changes without having to deal with the
> complexity of using Spring Security directly.
>
> This release includes significant enhancements, including:
> - upgrade to Spring Security 2.0
> - new support for LDAP/ActiveDirectory logins, including the option to
> store roles in the database, infer them from LDAP group membership, or both
> - new support for OpenID logins that integrate with your application's
> domain Users and Roles
> - made more of the configuration user-configurable, e.g. filter, logout
> handler, and role voter lists are now configurable - you can easily add
> your own, remove existing, or change the order
> - new configuration attributes were added, including mail server port and
> mail server JavaMailProperties to allow more control over mail sending and
> to allow usage of GMail SMTP
> - GrailsUser is now an interface, and GrailsDaoImpl was reworked to make
> subclassing or replacement easier to allow custom database user loading
> - added full suite of unit and integration tests, and also automated
> functional tests using WebTest
> - new wrapper for Acegi events that calls optional application-defined
> closures when events fire
> - moved all classes to packages
> - enhanced Ajax login support including a brief tutorial
> - lots of updates to the documentation
> (http://grails.org/AcegiSecurity+Plugin)
> - bug fix - bypassed DigestUtils for password encryption to allow use of
> any supported codec
>
> The plugin and source code are available for download here:
>
> http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/
>
> For more information on the Grails Acegi plugin, visit the Grails wiki
> page:
>
>   http://grails.org/AcegiSecurity+Plugin
>
> Feedback, suggestions for improvement and contributions are always welcome.
>
>
> Cheers!
> ----------------
> The Grails Acegi plugin team
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[burtbeckwith]

Yep, just the opposite :)

There were a lot of implementation changes, but I tried to limit the impact on
users. The upgrade process is described here:
http://grails.org/AcegiSecurity+Plugin+-+Upgrading+from+0.2.x+to+0.3

Basically all you have to do is rename AcegiConfig.groovy to
SecurityConfig.groovy and make a couple of small edits in that file. You also
need to update your IDE sourcepaths and classpath since the folders and jars
changed, and tweak a few imports.

It should be pretty painless. I've been working with several people off-list
who were trying out the snapshot builds and they were very helpful in finding
upgrade issues.

Let me know if you have any problems.

Burt

On Wednesday 30 April 2008 8:19:14 pm Peter Cold wrote:

> Hi Burt-
> It sounds like there is not a real smooth upgrade path from 0.2 due to the
> drastic improvements that have been made here.  Am I way off base on that?
> I'd like to get on the latest rev with spring security 2.0, but don't know
> if I have time to work through the implementation again at this time...
>
> -Peter
>
>
>
>
>
> On Wed, Apr 30, 2008 at 4:59 PM, Burt Beckwith <burt@...>
>
> wrote:
> > I don't know of any issues with 1.0.1 wrt the Acegi plugin.
> >
> > Burt
> >
> > On Wednesday 30 April 2008 7:12:29 pm Rahul Jain wrote:
> > > Thanks for the great job with the plugin !
> > >
> > > One question I couldn't answer from the documentation: what is the
> >
> > minimum
> >
> > > rev of grails needed to run acegi plugin 0.3 ? I see that you have used
> > > grails 1.0.2 in the examples. Will grails 1.0.1 or earlier releases
> > > work with it as well ?
> > >
> > > -Rahul
> > >
> > >
> > > ----- Original Message ----
> > > From: Tsuyoshi Yamamoto <mottsnite@...>
> > > To: user@...
> > > Sent: Wednesday, April 30, 2008 6:37:08 AM
> > > Subject: [grails-user] ANN: Acegi Plugin 0.3 released
> > >
> > > The Grails Acegi plugin team is pleased to announce the release of
> >
> > version
> >
> > > 0.3 of the plugin.
> > >
> > > The Acegi plugin simplifies the work involved in integrating Acegi
> >
> > Security
> >
> > > into Grails applications. By combining a core configuration with
> > > user-specified options and overrides, it creates a best-practice
> > > configuration of Spring Security in any Grails application while
> >
> > allowing
> >
> > > developers to make config changes without having to deal with the
> > > complexity of using Spring Security directly.
> > >
> > > This release includes significant enhancements, including:
> > > - upgrade to Spring Security 2.0
> > > - new support for LDAP/ActiveDirectory logins, including the option to
> > > store roles in the database, infer them from LDAP group membership, or
> >
> > both
> >
> > > - new support for OpenID logins that integrate with your application's
> > > domain Users and Roles
> > > - made more of the configuration user-configurable, e.g. filter, logout
> > > handler, and role voter lists are now configurable - you can easily add
> > > your own, remove existing, or change the order
> > > - new configuration attributes were added, including mail server port
> >
> > and
> >
> > > mail server JavaMailProperties to allow more control over mail sending
> >
> > and
> >
> > > to allow usage of GMail SMTP
> > > - GrailsUser is now an interface, and GrailsDaoImpl was reworked to
> > > make subclassing or replacement easier to allow custom database user
> > > loading - added full suite of unit and integration tests, and also
> > > automated functional tests using WebTest
> > > - new wrapper for Acegi events that calls optional application-defined
> > > closures when events fire
> > > - moved all classes to packages
> > > - enhanced Ajax login support including a brief tutorial
> > > - lots of updates to the documentation
> > > (http://grails.org/AcegiSecurity+Plugin)
> > > - bug fix - bypassed DigestUtils for password encryption to allow use
> > > of any supported codec
> > >
> > > The plugin and source code are available for download here:
> > >
> > > http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/
> > >
> > > For more information on the Grails Acegi plugin, visit the Grails wiki
> > > page:
> > >
> > >   http://grails.org/AcegiSecurity+Plugin
> > >
> > > Feedback, suggestions for improvement and contributions are always
> >
> > welcome.
> >
> > > Cheers!
> > > ----------------
> > > The Grails Acegi plugin team
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe from this list, please visit:
> > >
> > >     http://xircles.codehaus.org/manage_email
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >    http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Peter Cold]

Fantastic.  Thanks!  I'll let you know how it goes...

On Wed, Apr 30, 2008 at 5:31 PM, Burt Beckwith <burt@...> wrote:

Yep, just the opposite :)

There were a lot of implementation changes, but I tried to limit the impact on
users. The upgrade process is described here:
http://grails.org/AcegiSecurity+Plugin+-+Upgrading+from+0.2.x+to+0.3

Basically all you have to do is rename AcegiConfig.groovy to
SecurityConfig.groovy and make a couple of small edits in that file. You also
need to update your IDE sourcepaths and classpath since the folders and jars
changed, and tweak a few imports.

It should be pretty painless. I've been working with several people off-list
who were trying out the snapshot builds and they were very helpful in finding
upgrade issues.

Let me know if you have any problems.

Burt

On Wednesday 30 April 2008 8:19:14 pm Peter Cold wrote:
> Hi Burt-
> It sounds like there is not a real smooth upgrade path from 0.2 due to the
> drastic improvements that have been made here.  Am I way off base on that?
> I'd like to get on the latest rev with spring security 2.0, but don't know
> if I have time to work through the implementation again at this time...
>
> -Peter
>
>
>
>
>
> On Wed, Apr 30, 2008 at 4:59 PM, Burt Beckwith <burt@...>
>
> wrote:
> > I don't know of any issues with 1.0.1 wrt the Acegi plugin.
> >
> > Burt
> >
> > On Wednesday 30 April 2008 7:12:29 pm Rahul Jain wrote:
> > > Thanks for the great job with the plugin !
> > >
> > > One question I couldn't answer from the documentation: what is the
> >
> > minimum
> >
> > > rev of grails needed to run acegi plugin 0.3 ? I see that you have used
> > > grails 1.0.2 in the examples. Will grails 1.0.1 or earlier releases
> > > work with it as well ?
> > >
> > > -Rahul
> > >
> > >
> > > ----- Original Message ----
> > > From: Tsuyoshi Yamamoto <mottsnite@...>
> > > To: user@...
> > > Sent: Wednesday, April 30, 2008 6:37:08 AM
> > > Subject: [grails-user] ANN: Acegi Plugin 0.3 released
> > >
> > > The Grails Acegi plugin team is pleased to announce the release of
> >
> > version
> >
> > > 0.3 of the plugin.
> > >
> > > The Acegi plugin simplifies the work involved in integrating Acegi
> >
> > Security
> >
> > > into Grails applications. By combining a core configuration with
> > > user-specified options and overrides, it creates a best-practice
> > > configuration of Spring Security in any Grails application while
> >
> > allowing
> >
> > > developers to make config changes without having to deal with the
> > > complexity of using Spring Security directly.
> > >
> > > This release includes significant enhancements, including:
> > > - upgrade to Spring Security 2.0
> > > - new support for LDAP/ActiveDirectory logins, including the option to
> > > store roles in the database, infer them from LDAP group membership, or
> >
> > both
> >
> > > - new support for OpenID logins that integrate with your application's
> > > domain Users and Roles
> > > - made more of the configuration user-configurable, e.g. filter, logout
> > > handler, and role voter lists are now configurable - you can easily add
> > > your own, remove existing, or change the order
> > > - new configuration attributes were added, including mail server port
> >
> > and
> >
> > > mail server JavaMailProperties to allow more control over mail sending
> >
> > and
> >
> > > to allow usage of GMail SMTP
> > > - GrailsUser is now an interface, and GrailsDaoImpl was reworked to
> > > make subclassing or replacement easier to allow custom database user
> > > loading - added full suite of unit and integration tests, and also
> > > automated functional tests using WebTest
> > > - new wrapper for Acegi events that calls optional application-defined
> > > closures when events fire
> > > - moved all classes to packages
> > > - enhanced Ajax login support including a brief tutorial
> > > - lots of updates to the documentation
> > > (http://grails.org/AcegiSecurity+Plugin)
> > > - bug fix - bypassed DigestUtils for password encryption to allow use
> > > of any supported codec
> > >
> > > The plugin and source code are available for download here:
> > >
> > > http://plugins.grails.org/grails-acegi/tags/RELEASE_0_3/
> > >
> > > For more information on the Grails Acegi plugin, visit the Grails wiki
> > > page:
> > >
> > >   http://grails.org/AcegiSecurity+Plugin
> > >
> > > Feedback, suggestions for improvement and contributions are always
> >
> > welcome.
> >
> > > Cheers!
> > > ----------------
> > > The Grails Acegi plugin team
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe from this list, please visit:
> > >
> > >     http://xircles.codehaus.org/manage_email
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Helmut Denk]

2 proposals for change can be found here:

Grails Acegi ACL Howto

An updated Grails Acegi plugin

this was published in the blogs only a few weeks ago.
its very promising how quick the changes made
it into the plugin-release.

thanks to the committers and tsuyoshi for this
flexibility.

what would be nice IMO is an example for
adapting cas-sso. i played with this about one year
ago and got it to run applying an ugly hack.
a clean solution of this (changing plugin-config
only) based on 0.3 is very welcome.

have a nice time

[robottaway]

Just thought I'd chime in and say thanks. I've been using the 0.2 release for a long time and found it very useful. My 2 cents: the plugin makes a very good start for any web app. I used it to create the boilerplate Acegi setup, and then made lots and lots of customizations to it. Please keep it simple as I will be doing more of the same in other projects and love the speed with which this plugin gets me up and going. Maybe the plugin could use more targets for adding extra complex configurations of Acegi?

cheers,
Rob

[burtbeckwith]

Could you describe some examples of what you're looking for?

Burt

On Thursday 01 May 2008 4:40:11 am robottaway wrote:

> Just thought I'd chime in and say thanks. I've been using the 0.2 release
> for a long time and found it very useful. My 2 cents: the plugin makes a
> very good start for any web app. I used it to create the boilerplate Acegi
> setup, and then made lots and lots of customizations to it. Please keep it
> simple as I will be doing more of the same in other projects and love the
> speed with which this plugin gets me up and going. Maybe the plugin could
> use more targets for adding extra complex configurations of Acegi?
>
> cheers,
> Rob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[burtbeckwith]

I integrated CAS with Acegi in a non-Grails app a while back, so I can add in
CAS support if there's interest. The approach I took then was to figure out a
generic way of adding in SSO since we didn't know which SSO providers our
customers would be using. So hopefully I could add in similar functionality
to the plugin to make integrating with SiteMinder, Crowd, etc. easier.

Burt

On Thursday 01 May 2008 4:16:07 am Helmut Denk wrote:

> 2 proposals for change can be found here:
>
> http://blog.bruary.net/2008/04/grails-acegi-acl-howto.html Grails Acegi ACL
> Howto
>
> http://burtbeckwith.com/blog/?p=60 An updated Grails Acegi plugin
>
> this was published in the blogs only a few weeks ago.
> its very promising how quick the changes made
> it into the plugin-release.
>
> thanks to the committers and tsuyoshi for this
> flexibility.
>
> what would be very nice IMO is an example for
> adapting cas-sso. i played with this about one year
> ago and got it to run but only by an uggly hack.
>
> have a nice time

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Helmut Denk]

hi burt,

sso-adaption would make grails even more attractive from an
enterprise point of view ...

i could upgrade my grails-apps security without having to
reintegrate 'handmade' cas-adaption again and again.

have a nice time

burtbeckwith wrote:

I integrated CAS with Acegi in a non-Grails app a while back, so I can add in
CAS support if there's interest. The approach I took then was to figure out a
generic way of adding in SSO since we didn't know which SSO providers our
customers would be using. So hopefully I could add in similar functionality
to the plugin to make integrating with SiteMinder, Crowd, etc. easier.

Burt

On Thursday 01 May 2008 4:16:07 am Helmut Denk wrote:
> 2 proposals for change can be found here:
>
> http://blog.bruary.net/2008/04/grails-acegi-acl-howto.html Grails Acegi ACL
> Howto
>
> http://burtbeckwith.com/blog/?p=60 An updated Grails Acegi plugin
>
> this was published in the blogs only a few weeks ago.
> its very promising how quick the changes made
> it into the plugin-release.
>
> thanks to the committers and tsuyoshi for this
> flexibility.
>
> what would be very nice IMO is an example for
> adapting cas-sso. i played with this about one year
> ago and got it to run but only by an uggly hack.
>
> have a nice time


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[robottaway]

Sure thing I'll give two, a stark naked base install vs. a more complex database backed install.

To start with the install could include the InMemoryDaoImpl and form based auth filter chain. It would provide the ability to the developer to begin creating rules about authorization, while not having to worry about the access control aspect. I hacked the plugin to do this first thing when just getting started with my site. It made development easy, I just hand wrote in two users in the plugin config file.

Second, for the more complex case, a target to generate a User domain class (implementing UserDetails) and the UserDetailsService implementation (as a Grails service of course). This should also create the proper controllers to do CRUD on the user object, add/update/delete accounts, lock/unlock accounts, etc. etc. I eventually wrote my own User model and service, but some may prefer to just use ones generated by the plugin.

I believe the benefit here is some people will want to just add quickly the Acegi filters and stack to their project. They want the basics because they plan to write the authentication and access control implementations. For those that want the user access control right away #2 will give them that. A project such as a blog should allow users to create accounts and leave comments. The user model can be very simple so #2 could be a time saving measure in such a case.

regards,
Rob

burtbeckwith wrote:

Could you describe some examples of what you're looking for?

Burt

On Thursday 01 May 2008 4:40:11 am robottaway wrote:
> Just thought I'd chime in and say thanks. I've been using the 0.2 release
> for a long time and found it very useful. My 2 cents: the plugin makes a
> very good start for any web app. I used it to create the boilerplate Acegi
> setup, and then made lots and lots of customizations to it. Please keep it
> simple as I will be doing more of the same in other projects and love the
> speed with which this plugin gets me up and going. Maybe the plugin could
> use more targets for adding extra complex configurations of Acegi?
>
> cheers,
> Rob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hartsock]

I'm in the same boat so I'd love to see something that could do CAS+Acegi simply.


hi burt,

sso-adaption would make grails even more attractive from an
enterprise point of view ...

i could upgrade my grails-apps security without having to
reintegrate 'handmade' cas-adaption again and again.

have a nice time

burtbeckwith wrote:

I integrated CAS with Acegi in a non-Grails app a while back, so I can add in
CAS support if there's interest. The approach I took then was to figure out a
generic way of adding in SSO since we didn't know which SSO providers our
customers would be using. So hopefully I could add in similar functionality
to the plugin to make integrating with SiteMinder, Crowd, etc. easier.

Burt

On Thursday 01 May 2008 4:16:07 am Helmut Denk wrote:
> 2 proposals for change can be found here:
>
> http://blog.bruary.net/2008/04/grails-acegi-acl-howto.html Grails Acegi ACL
> Howto
>
> http://burtbeckwith.com/blog/?p=60 An updated Grails Acegi plugin
>
> this was published in the blogs only a few weeks ago.
> its very promising how quick the changes made
> it into the plugin-release.
>
> thanks to the committers and tsuyoshi for this
> flexibility.
>
> what would be very nice IMO is an example for
> adapting cas-sso. i played with this about one year
> ago and got it to run but only by an uggly hack.
>
> have a nice time


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email