Hi Jan, If you read the 2.1.2 documentation: at the and of the authentication-chapter, there's an excercise...:
...But the auth-loggedIn action does not give the included pipeline access to the authentication context belonging to the handler. If you want this, you have to nest the auth-protect action inside! <map:match pattern"start"> <map:act type="auth-loggedIn"> <!-- check authentication --> <map:parameter name="handler" value="myhandler"/> <map:act type="auth-protect"> <!-- give access to the context --> <map:parameter name="handler" value="myhandler"/> <map:generate src="getinfofromcontext.xml"/> <map:transform src="session"/> <map:transform src="toHTML"/> <map:serialize/> </map:act> </map:match> > Von: Jan Wielgus <[EMAIL PROTECTED]> > Antworten an: [EMAIL PROTECTED] > Datum: Sat, 25 Oct 2003 16:21:14 +0200 (MET DST) > An: [EMAIL PROTECTED] > Betreff: [newbie] Authentication-context in the auth.-framework > > Hello, > > in the authentication framework documentation you can read: > > "The authentication context is only available to the session transformer if > the pipeline, the transformer is running in, is associated to the > (authentication) handler. Or putting it in other words: you have to use the > auth-project action in that pipeline. Otherwise the authentication context is > not available." > > My question is: where exactly do I have to use the auth-project action how > should I write it? Could anyone give a simple excerpt of a sitemap where this > action is used? Many thanks in advance. > > Jan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
