Hi! I've got a real Problem with the authentication-framework. (By the way, I'm not 100% sure that the authentication-framework is the reason, but guess it is).
I have a more or less complicated role-managment in my project.
If a user want to change his profile, he logs in and does a click on a
edit-profile-link. Then a new window is opening and the user does his changes.
After he did, there is a writesource close to the on in the portal fw and I
update all changes in the authentication-context in that way:
<session:setxml context="authentication" path="/authentication/data/name">
<session:getxml context="request" path="/parameter/name"/>
</session:setxml>
<session:setxml context="authentication" path="/authentication/data/salutation">
<session:getxml context="request" path="/parameter/salutation"/>
</session:setxml>
<session:setxml context="authentication" path="/authentication/data/company">
<session:getxml context="request" path="/parameter/company"/>
</session:setxml>
...
Afterwards the user closes the window and should work on in the parent/main
window. Unfortunately thats not possible, because every link protected
by <map:act type="auth-loggedIn"> results in a NullPointerException. Links
protected by auth-protect are working perfectly. Using auth-protect is not
possible because I can not use the redirect.
If I don't update the session like described above, I can work on.
But I don't know how to refresh the authentication-context except with a manual logout
/ login
done by the user, which is no solution for me.
Who can help??
Freddy
pgp00000.pgp
Description: PGP signature
