Postby ConvertFromOldNGs » Fri Aug 07, 2009 12:54 pm
by Patwos >> Fri, 28 Oct 2005 2:46:53 GMT
This is by no means a complete list of options, but some of the following may be useful for your requirements:
1. Don't install a licence key that allows the Jade IDE to be run to prevent users from using the IDE Inspector or JadeScripts to get at the data.
2. If you must have the Jade IDE available, make use of the DevelopmentSecurityLibrary setting in the [JadeSecurity] section of the ini file to restrict who can run the IDE. (See Install & Admin Guide for further info.)
3. If running thin clients, use the AllowSchemaAndApp setting in the [JadeAppServer] section of the ini file to restrict what applications can be run from more publicly visible AppServers. eg: AppServers where users connect across the Internet. (See Install & Admin Guide for further info.)
4. Ensure you use SSL encryption on the thin client connections. (See Install & Admin Guide for further info.)
5. To prevent users running the RootSchema's Schema Inspector application to navigate your data, implement Object::allowedToInspect at your highest schema level to return false and only override to return true for those schema classes you want to be available to the Schema Inspector application. (See Object Manager Guide for further info.)
It is also important to make sure your servers are appropriate protected by suitable firewall and router rules.
Hope that helps,
Pat.