Hi James,
Thanks for the answer.. you were right we needed the hivemind-utils.jar file
also.
I have two more questions:
1) Now our application works fine when we are browsing the public
(non-secured) pages and when we are testing one page with Secured annotation
we get the Basic Authentication Login form... we do not want to use this
later, but for testing if the authentication is working we try to login
using this and when we do so, we get an exception stating:
HTTP Status 500 -
type: Exception report
message: description The server encountered an internal error () that
prevented it from fulfilling this request.
exception: org.apache.hivemind.ApplicationRuntimeException: Unable to
construct service hivemind.acegi.dao.UserDetailsService: Property
'beanFactory' of <SingletonProxy for
hivemind.lib.DefaultSpringBeanFactoryHolder(org.apache.hivemind.lib.SpringBeanFactoryHolder)>
is null. [context:/WEB-INF/hivemodule.xml, line 59, column 68]
org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructNewServiceImplementation(
AbstractServiceModelImpl.java:166)
...
Here is the acegi code in our hivemodule.xml:
<contribution configuration-id="hivemind.ApplicationDefaults">
<default
symbol="hivemind.acegi.dao.passwordEncoder"
value="org.acegisecurity.providers.encoding.PlaintextPasswordEncoder"/>
<default symbol="hivemind.acegi.dao.systemWideSalt" value="" />
</contribution>
<implementation service-id="hivemind.acegi.dao.UserDetailsService">
<invoke-factory service-id="hivemind.lib.SpringLookupFactory">
<lookup-bean name="jdbcDaoImpl" />
</invoke-factory>
</implementation>
<contribution configuration-id="hivemind.acegi.AccessDecisionVoters">
<voter object="instance:org.acegisecurity.vote.RoleVoter" />
</contribution>
And here is the spring bean:
<bean id="jdbcDaoImpl"
class="org.acegisecurity.userdetails.jdbc.JdbcDaoImpl">
<property name="dataSource">
<ref bean="dataSource"/>
</property>
<property name="usersByUsernameQuery">
<value>
SELECT user_name as username, user_password as
password, enabled as
ENABLED FROM app_user WHERE user_name=?
</value>
</property>
<property name="authoritiesByUsernameQuery">
<value>
SELECT user_name as username, user_role as
authority FROM app_user_role
WHERE user_name=?
</value>
</property>
</bean>
2) When we are doing the form validation we actually have another delicate
problem. We have a couple of entry points to our system (domain names) that
goes to a HomeDispatcher that redirects it to different pages depending on
the incoming Domain Name. Some of these goes to a couple of public pages
that each have a login component that takes these users to a admin area for
the public pages. The other entry point is for our in house application that
starts directly with a login page. The question is: What is the best way of
doing the form based login? I saw some postings between you and Robin
Ericsson where he said he sent you a working code for form based
authentication
I guess this is not included in tapestry-acegi project... could you post
this code here in the form until then... I think a lot of people are
interested in that solution.
Thanks again for your help
Cheers,
Jacob
--
View this message in context:
http://www.nabble.com/Exception-when-trying-to-configure-tapestry-acegi.jar-tf3142373.html#a8731641
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
