Hello,
When the user gets authenticated I am also reading
information about their skin preference for inclusion
into the authentication session. Later on in the
portal sitemap, I am using this skin variable to
determine what images and CSS to load. For the login
page, an anonymous user with a def
* Andrew MacDonald:
> How can I set the authentication context before
> matching on the CSS and images?
Could you please provide us with relevant parts of your
sitemap?
TIA,
--
Jean-Baptiste Quenot
Anyware Technologies
http://www.anyware-tech.com/
Yes, of course. I should've done that in the original
post, sorry.
Here's the authentication part where the skin variable
is added (from user-data-test.xml):
...
Here's the authentication context:
an
* Andrew MacDonald:
> Later on, in the main pipeline I have this:
>
>
>
>value="portal-handler"/>
>src="skins/{skin}/css/{1}.css"/>
>
>
If the user is not logged in, how do you expect the CSS to be loaded?
You could maybe have an unprotected pipeline for anonymous user
When the login/welcome page is loaded, the portal does
a auto-login of an anonymous user. For the anonymous
user it loads up a default skin for displaying the
page. Then, when a user logs in, the skin is changed
to whatever their preference is. I was able to fix
the problem, it turns out I'd for
