Hi Seth,
I restrict what users can and can't do by running them through a 'traffic cop' of sorts.
I have a navigation document which performs 2 functions: 1 is to generate the menus that the program displays and the other is to determine who can have access to a particular portion of the application.

For example:

A section of my navigation.xml looks like this:
    <menu_category type="non-visible">
        <menu label="non-visible">
            <menu-item href="" label="processLinks" roleName="Public" role="1"/>
            <menu-item href="" label="noticeEdit" roleName="Public" role="1"/>
            <menu-item href="" label="searchHrcy" roleName="Admin" role="256"/>
            <menu-item href="" label="getChildNodesOnly" roleName="Public" role="1"/>
       </menu>
    </menu_category>

When a user tries to access a particular flow function like 'searchHrcy.do', their user permissions (a global variable obtained at login) is compared to the role attribute of the menu-item. If they don't have sufficient privileges to access this function then they are redirected.
Similarly if they attempt to access and function not listed in the navigation.xml, an error is generated and they are redirected.
All this role checking and redirection is handled by flow. This could be extended to include any pipeline calls as well by listing them in the navigation document and using flow to call sendPage(menu-item).

I hope this makes sense. The application I am writing required really fine grained access level so I knocked up this 'traffic cop' to check every public flow function.
If you need more detail, let me know.

Regards
Tony


Seth Foss wrote:
How do I restrict a user from accessing pipelines outside of flowscript. I can figure out how to redirect un-authenticated users to a login page, but if logged-in users manually enter a pipeline into the address bar, how do I redirect them into my flowscript. I plan on using continuations, so Submits and Nexts will not direct to the correct pages without the flowscript running.
 
Seth Foss

--

This email is from Civica Pty Limited and it, together with
any attachments, is confidential to the intended recipient(s)
and the contents may be legally privileged or contain
proprietary and private information. It is intended solely
for the person to whom it is addressed. If you are not an
intended recipient, you may not review, copy or distribute
this email. If received in error, please notify the sender
and delete the message from your system immediately. Any
views or opinions expressed in this email and any files
transmitted with it are those of the author only and may
not necessarily reflect the views of Civica and do not create
any legally binding rights or obligations whatsoever. Unless
otherwise pre-agreed by exchange of hard copy documents
signed by duly authorised representatives, contracts may not
be concluded on behalf of Civica by email. Please note that
neither Civica nor the sender accepts any responsibility for
any viruses and it is your responsibility to scan the email
and the attachments (if any). All email received and sent by
Civica may be monitored to protect the business interests of
Civica.

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to