Safety Features

Scriptcase 8 Suggestions
#1

It would be desirable if there would be a pre-integrated security, including the necessary websites for configuration.
The competitors product has PHPRunner because a solution could you take it as a template. That would erleichetern a developer’s work significantly.

#2

Re: Safety Features

It is there. In the menu you go to

File / New modules / Security

#3

Re: Safety Features

It’s poorly documented and can cause more problems than it’s worth. I agree with the OP, the PHPrunner solution has to be one of the best around.

#4

Re: Safety Features

Hi all,

I would like to share some of the security features with SC

  1. It has in-built security control in which needs to be enabled in each of forms works fine
  2. It has menu level security access control released from V5 good too.!

I presonally belived that security is one of important basci function for any project,

I had developed dymanic menu level security framework helps to manage menus dynamically and access control at users level

Aprart from that It is advised to follow

  1. Always use application inside the menu application (ie Call always “_self”)
  2. manage Session cookies on each forms inside the menu application
  3. Always enable security in the application

Regards
Dhana

#5

Re: Safety Features

Poorly documented, probably! I’ve just had a look at the PHPRunner site and the security does look better. More trouble than it’s worth though, what exactly are the troubles caused by it?

#6

Re: Safety Features

Poorly documented, probably! I’ve just had a look at the PHPRunner site and the security does look better. More trouble than it’s worth though, what exactly are the troubles caused by it?

A while back I posted here about the deployment issues I had. I have since worked out that the deployment problems I experience occur only once I try to use that security module feature in SC5.

For secured applications I’ll stick with PHPrunner for now until I get on top of SC5.

#7

Re: Safety Features

Yes, Poorly documented.

But you can set up your own security. Usually we use three tables:

  • Groups
  • Applications
  • Groups X Applications

So, basically you manage your user in waht groups they belong.

Through that, after the user loging, just select the applications that belongs to the group and use sc_apl_status to on to enable the application.

You can do more deep … if is a form application, you can choose if the user can delete, update or delete, using sc_apl_conf to enable or disable the application option dynamically.

There is many ways to do that.

Soon in our tutorial videos will have explaining everything about the deployment and the production environment and about the security too.