Upon closer inspection it turns out that no it isn't that simple.
This is it
<cfset iHasViewPermission = 1 />
<cfif isDefined("session.dmsec.authentication.lPolicyGroupIDs") and
listLen(session.dmsec.authentication.lPolicyGroupIDs)>
<!--- concatenate logged in group permissions with anonymous
group
permissions --->
<cfset lpolicyGroupIds =
session.dmsec.authentication.lPolicyGroupIDs & "," &
application.dmsec.ldefaultpolicygroups>
<cfelse>
<!--- user not logged in, assume anonymous permissions --->
<cfset lpolicyGroupIds = application.dmsec.ldefaultpolicygroups>
</cfif>
<cfset iHasViewPermission =
oAuthorisation.checkInheritedPermission( permissionName="View",
objectId=#qNav.objectID#, lPolicyGroupIds="#lpolicyGroupIds#" ) />
if iHasViewPermission eq 1 you're permitted (it can be -1, 0 or 1...
for whatever reason).
B.
On Oct 19, 11:14 am, bsmith <[EMAIL PROTECTED]> wrote:
> OK looking good at the moment, I've now got a members area with a
> custom login form, signups and password resets... pretty happy with
> how it's all come together.
>
> Just a quick "howto" question in regard to permissions - i just find
> the permissions stuff a bit hairy in version 3 (looking forward to
> 4.1)
>
> If the user is logged in, i need to check their "View" permission for
> a dmNavigation object before i display the link.
>
> Is it as simple as this?
>
> <cfset bHasPermission = true />
> <cfif request.loggedIn>
> <cfset bHasPermission = oAuthorisation.checkPermission( "View",
> #objectID#, #session.dmSec.authentication.lPolicyGroupIds# ) />
> </cfif>
>
> The assumption of permission might seem backwards, but the reasoning
> is that nav nodes need to be displayed when the user is anonymous in
> order to give them the login prompt, whereas if they're logged in and
> don't have permission, they don't need to see them.
>
> Cheers,
>
> B.
>
> On Sep 27, 1:16 pm, bsmith <[EMAIL PROTECTED]> wrote:
>
> > That's a neat way to do it, I was contemplating a custom display.cfm
> > to direct the users to the various forms.
>
> > Thanks Blair.
>
> > B.
>
> > On Sep 26, 1:40 pm, "Blair McKenzie" <[EMAIL PROTECTED]> wrote:
>
> > > The login page can be
> > > customised<http://docs.farcrycms.org:8080/confluence/display/FCDEV40/Customise+L...>by
> > > adding a
> > > login.cfm file to /yourproject/customadmin/login.
>
> > > Since this page is passed returnurl via URL, you could use this in a
> > > switch
> > > to include different login forms for different destinations. i.e. if
> > > returnurl contains "farcry" then the user is trying to access the admin
> > > console.
>
> > > Blair
>
> > > Yes. The login page is passed returnurl via URL.
>
> > > On 9/26/07, bsmith < [EMAIL PROTECTED]> wrote:
>
> > > > Hi All,
>
> > > > I'm adding a members area to a site... I plan to do this using dmUser,
> > > > with a custom Profile table, and assigning them to a newly created
> > > > Group with associated permissions.
>
> > > > Then i'll create node off the site tree, and assign the relevant
> > > > permissions, meaning when a user hits that node they'll be asked to
> > > > log in.
>
> > > > Now, I want to present the public-site users with a different login
> > > > screen than the farcry administrators... is there an easy way to do
> > > > this?
>
> > > > B.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
