Securing Developer's License Accesses

[ConvertFromOldNGs]

by tyc >> Mon, 19 Aug 2002 8:54:39 GMT

Hi Jade Developers,

Just need an opinion from the various installations that you all have. With a huge amount of CALs, and just 2 DAL, would it be better to have them as seperate license or combined into one.

My concern is that if the users found out how to get into the
developer's environment, it will be a huge security risk, but patching and modification is so much easier with Developer's license available.

Are there any ways to prevent certain users from accessing the Developer's environement, [ passwords, locking of stations etc] even though the license allows them to access?

Regards,
L.C. Lim

[ConvertFromOldNGs]

by allistar >> Mon, 19 Aug 2002 21:35:20 GMT

There is a DevelopmentSecurityLibrary tag in the [JadeSecurity]
section of the ini file that can point to a DLL that will be used to validate and control access in the development environment. The JOM
Guide has the relevant DLL information in Chapter 2 and the INI
setting is in the Install and Ops Guide.

Hope this helps,
Allistar.

------------------------------------------------------------------
Allistar Melville
Software Developer
Auckland, NEW ZEALAND

Greentree International,
Developer of Greentree Financial Software. ------------------------------------------------------------------

[ConvertFromOldNGs]

by jadesupport >> Tue, 20 Aug 2002 0:32:37 GMT

Further to Allistars response, if all your clients will be connecting via thin client, then you can also utilise the following settings in the [JadeAppServer] section of the ini file to restrict what applications are allowed to be run via an AppServer:

EnableAppRestrictions =true
AllowSchemaAndApp1 =<schemaName>,<appName1>
AllowSchemaAndApp2 =<schemaName>,<appName2>

etc.

Thanks,
Brian Johnstone,
JADE Support.

[ConvertFromOldNGs]

by tyc >> Tue, 20 Aug 2002 3:06:23 GMT

Hi Allistar and Brian,

Thank you for your advice.. It is a life-saver..
Will be experiementing with it..

Regards,
L.C. Lim

[ConvertFromOldNGs]

by torrie >> Tue, 20 Aug 2002 7:45:26 GMT

There is also the ability to deploy a system using the deployment (deploy) system files. This set of database files does not include the Jade Development environment. You can develop in a standard system and then load the schemas into the deployment system for the live system. None of the users would be able to run Jade over the live environment. I think the install process allows you to select deployment during the startup process. The disadvantage with this approach is that if you ever need to get onto the live system with the development environment you can't.

Torrie Moore
JBS Solutions

[ConvertFromOldNGs]

by Brett >> Tue, 20 Aug 2002 23:13:54 GMT

Hi Torrie,

We had a deployed Jade application that we 'upgraded' to a Jade Developement application.

Take a copy of your deployed Jade env. first.

This can be done be copying these files (_sys* and _jade*)
from the bin directory of a Developement env. with the same Jade version overtop of the Jade
deployed bin folder. Then reset timestamps on the deployed database. Should be all go.
I take no responsibility for any damage, etc.

Brett
Kinetix.