On May 10, 2004, at 11:54 AM, Nils wrote:
could you post an excerpt of your sitemap, please`?
Sure... sounds like you'd like to do something similar...? here ya go... ~mark
<!--
++ the authentication resource
-->
<map:match pattern="authenticate">
<map:act type="request">
<map:call function="authenticate">
<map:parameter name="resource" value="{request-param:resource}" />
</map:call>
</map:act>
</map:match>
<! -- invoked by flowscript above... -->
<map:match pattern="authenticate.result">
<map:generate type="jx" src="authentication/result.jx" />
<map:serialize type="xml" />
</map:match>
<!--
++ Our set-up of the Cocoon auth fw is a little unique here... we don't
++ have our own login page at all, instead we only
++ authenticate based on info ("?login:password") embedded in the
++ link from the XXXX end-user page. If the user is not
++ authenticated, we redirect them back to the XXXX login
++ page. The whole idea is to avoid the need for
++ double-authentication (once at XXXX, and once here). We
++ therefore need for our authentication resource to be requested for
++ any unauthenticated access to a protected resource, without
++ displaying any login form. Hence, we invoke the auth-login action
++ here, in the redirect-to resource of the authentication handler,
++ whereas normally it would be invoked from the handler of a login
++ form.
-->
<map:match pattern="login">
<map:act type="auth-login">
<map:parameter name="handler" value="auth-agent" />
<map:parameter name="parameter_resource" value="{request-param:resource}" />
<map:redirect-to uri="{request-param:resource}" />
</map:act>
<map:redirect-to uri="https://xxxxxxxxxx/login.pl"; />
</map:match>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
