Hi Geert, Saturday, November 11, 2006, 3:33:06 PM, you wrote:
GB> Hi Maxim, >> I'm starting to use RIFE and have some question: GB> Welcome to the list and I hope we can help you out with your questions! Thank you >> First portion for authorization: >> >> 1. I create users memory authorization (i read about it here >> http://rifers.org/wiki/display/RIFE/Authentication+system+internals) >> >> but i didn't find there anything about logout. >> >> How can i implement logout ? GB> http://rifers.org/wiki/display/RIFE/Logout+element+flavours I did it but user could view restricted pages after logout. Here's my elements: <departure srcid="Logout"/> <element id="Logout" file="rife/logout/passthrough/memory.xml" url="/logout"> <flowlink srcexit="logged_out" destid="home"/> <property name="authvar_type">cookie</property> </element> <element id="AuthElement" extends="rife/authenticated/memory.xml"> <property name="template_name">auth_login</property> <property name="role">admin</property> <property name="authvar_type">cookie</property> <submission name="credentials"> <param name="login"/> <param name="password"/> </submission> <childtrigger name="authid"/> <incookie name="authid"/> <outcookie name="authid"/> <incookie name="rememberid"/> <outcookie name="rememberid"/> </element> <group inherits="AuthElement"> <element implementation="com.frnews.web.rife.component.admin.AdminHome"> <exit name="logout"/> <flowlink srcexit="logout" destid="Logout"/> </element> <element implementation="com.frnews.web.rife.component.admin.SecondAdmin"> <exit name="Logout"/> </element> </group> And in admin element template i have logout link: <p><a href="${v EXIT:QUERY:logout/}">logout</a></p> First time user is asked for enter login. Then he can view all restricted pages. When he clicks logout, he goes to home page. But if he enter restricted page URL in his browsser, he sees this page and can continue to see other pages. What am i doing wrong ? >> 2. is it possible that some pages will be accessible for some roles >> not just one ? GB> This is currently not supported by the standard RIFE RoleUsers GB> authentication implementation. You can however customize the current GB> way of working by extending the RoleUserAuthenticated element and the GB> associated managers. I realize that this is too much work, and GB> probably too complicated for a new-comer to the framework, so please GB> file an issue about this in Jira and I'll see about getting it GB> implemented. OK, i'll do it but at first i want to decribe it more detailed. I have pages which can be viewed by anonymous users but when user logins he sees this page with other elements. And when admin sees this page then another element are visible. Also i need that some pages will be accessable only by admins and editors. Are both of my needs not implemented in RIFE ? >> i don't what it is bug in rife 1.5.1 or resin 3.0.21 or maybe i did >> something wrong. Any ideas ? GB> I think this was answered on IRC, right? When you run it from within GB> IDEA this happens, but not with standalone Resin, correct? Yes, this question is closed Also is it possible to make CRUD page customization with minimal efforts ? I want to add custom input field which will not store in CRUD element but in file system. -- Best regards, Maxim mailto:[EMAIL PROTECTED] _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
