have you implemented acegi authentication as described here?

So that I understand your problem: your authentication provider does not provide authentication information correctly?

<quote>Acegi retrieves all the authentication information from database while loading the application itself.</quote>

Why does it do this? What are the differences compared to the “standard” acegi configuration?

Cheers,
Martin

I am implementing Acegi in my JSF application. Both authentication and authorization is working fine with my application. But If i register a new user in my application then i have to stop and restart the server inorder to authenticate that new user. Else it shows “user not found” message . Acegi retrieves all the authentication information from database while loading the application itself. It was not holding the newly registered user’s details. i searched in the net and tried to instantiate the Acegi’s application context from its xml files explicitly when a new user is activated. But it was not working. How can we add a new user to Authentication object??

Now I see what’s the reason why you use this in your faces-config.

Many thanks!

<redirect/>

in the faces-config for these navigation cases?

welcome.xhtml:

<h:form>
	<h:panelGrid border="1" columns="1">
		<h:commandLink action="toUser">
			<h:outputText value="To User"></h:outputText>
		</h:commandLink>
		<h:commandLink action="toAdmin">
			<h:outputText value="To Admin"></h:outputText>
		</h:commandLink>
		<h:commandLink action="toSupervisor">
			<h:outputText value="To Supervisor"></h:outputText>
		</h:commandLink>
	</h:panelGrid>
</h:form>
...

Admni.xhtml

<h:form>
	<h:commandLink action="toSupervisor">
		<h:outputText value="To Supervisor"></h:outputText>
	</h:commandLink>
</h:form>
...

	<filter-mapping>
		<filter-name>Acegi Filter Chain Proxy</filter-name>
		<url-pattern>/*</url-pattern>
		<dispatcher>FORWARD</dispatcher>
		<dispatcher>REQUEST</dispatcher>
	</filter-mapping>

you might try to add a

<dispatcher>FORWARD</dispatcher>

element to your acegi filter mapping, so that this is applied to any forward targets matching the specified servlet or URL pattern.

Cheers,
Martin

<pre>

followed by a

<code>

tag around your code.