Jump to content

This topic is 7435 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I know IWP isn't terrible secure to begin with, but I want to at least try to lock my solution down as much as possible. The database is powering a signup/registration page (why they couldn't find someone to make something with PHP or similar is beyond me... confused.gif) so the users need much more access than the usual setup.

As it stands now, a script locks the user to one restricted layout and locks out the menu items on load and creates a new record.

Users have to be able to create, modify and delete records, however, becase the only way I could make an "unsubscribe" function compatible with IWP was to set info from the "new" record to a global field, delete the record, and then search old records for places where the global field matches, to then modify that record. Not the cleanest answer, but it works...

I'm a little worried though that it's too much acccess for the general web-using public. If I restrict users to a data-entry mode but allow them to run scripts with full-access, will that work? IE, if my script has full privileges and it runs a delete command, will the script work when the user personally lacks privileges to delete?

This topic is 7435 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.