Hi Joe,
I have a question around security settings. I’m trying to work out the best way to deal with the Survey Feature without reworking what is already part of the mojo security framework.

The scenario is I would like to achieve the following:

• Allow for anonymous surveys
This is fine, if an anonymous survey then don’t do any checks.

• Allow for authenticated surveys
So if I do this check:

if (HttpContext.Current.Request.IsAuthenticated)
{
Display the start message of the survey in the ascx
}
else
{
Display some message saying you must log in to take this survey
}

And then do this check in the separate pages for any hack attempts to go direct to the survey.

• Allow a survey to be targeted at a group of users
I’m thinking something around the admin adds all survey users to a new role e.g. “OfficeStaffSurvey” and then restricts the page with the content to this role and admin only.

Then do a test in each survey completion page and the ascx…

WebUser.IsInRole(CurrentPage.AuthorizedRoles)
Although this may fall down as CurrentPage.AuthorizedRoles returns comma seperated list I think, so if an admin adds more then one role it may break?

• Allow specific users to add surveys/edit surveys
I think this should do the trick.

if (!WebUser.HasEditPermissions(siteSettings.SiteID, ModuleId, CurrentPage.PageID))
{
SiteUtils.RedirectToEditAccessDeniedPage();
}

I hope this makes sense. I have ideas how to do everthing but I don’t want to reinvent something that could already support these scenarios. Thanks in advance for any help!

Cheers,
Rob

Thanks Joe. I'll follow the simple route you describe.