Jacob,
It's definitely possible.
I'm also using Spring, and Hibernate, but this time around, I'm using an
InMemoryDAO and LDAP (Active Directory) for authentication.
By comparing the configuration I did on a Spring-driven T4 Acegi integration
with the code in tapestry5-acegi, I finally started to understand both Acegi
and tapestry-ioc.
You might want to back away from the Hibernate DAO initially just to get the
basics running. You can then either replace InMemoryDao or just add on your
own Hibernate DAO.
The in-memory dao gives something great for development, so here's what I
did with my AppModule:
1) clear the password salt by contributing to application defaults (easier
for development with the InMemoryDao:
public static void contributeApplicationDefaults(
MappedConfiguration<String, String> configuration)
{
....
configuration.add("acegi.loginform.url", "/login");
configuration.add("acegi.password.salt", "");
configuration.add("acegi.accessDenied.url", "/SecurityException");
}
2) configure the InMemoryDaoImpl
public final UserDetailsService buildInMemoryDaoImpl() throws Exception
{
InMemoryDaoImpl dao = new InMemoryDaoImpl();
Properties props = new Properties();
props.put("user","user,ROLE_USER");
props.put("supervisor","supervisor,ROLE_SUPERVISOR");
props.put("admin","admin,ROLE_ADMIN");
UserMap userMap = new UserMap();
UserMapEditor.addUsersFromProperties(userMap, props);
dao.setUserMap(userMap);
dao.afterPropertiesSet();
return dao;
}
3) contribute a provider manager (I've left in my ldap stuff so you can see
how additional auth methods can be added -- just delete any mention of LDAP
below):
public static void contributeProviderManager(
OrderedConfiguration<AuthenticationProvider> configuration,
@InjectService("DaoAuthenticationProvider") AuthenticationProvider
daoAuthenticationProvider, @InjectService("LdapAuthenticationProvider")
AuthenticationProvider ldapAuthenticationProvider){
configuration.add("daoAuthenticationProvider",daoAuthenticationProvider);
configuration.add("ldapAuthenticationProvider",ldapAuthenticationProvider);
}
> -----Original Message-----
> From: Jacob Bergoo [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 24, 2008 10:29 PM
> To: users@tapestry.apache.org
> Subject: RE: T5: Problems with Tapestry5-Acegi
>
>
> Thanks Jonathan for your quick answer...
> accually I am Using T5, Spring 2.5.1, Hibernate 3.2 so I am looking for a
> solution where I can Use the Acegi for the security and using the @Secure
> annotation for pages/methos... I have seen another wiki page that shows on
> how to set up the Acegi to work with Spring Application Context file, but
> it
> stated that it didn't work with @Secure annotations... so that means that
> all the configurations are done by mapping folder structures and page
> names
> with uer roles... I rather not do that....I want to be able so see on the
> pages I am working on what roles that are allowed for that page...
>
> So Is there a way of making Tapestry5-Acegi project for my configuration
> or
> do I need to choose the less wanted solution?
>
> Thanks again for your help,
> Jacob
> --
> View this message in context: http://www.nabble.com/T5%3A-Problems-with-
> Tapestry5-Acegi-tp16266687p16267063.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 2969 (20080324) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2969 (20080324) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
