What controls a user's ability to connect to a K2 environment with the SmartObject Services tester? For example, we desire to prevent our development team, who use this tool, from connecting to K2PD. (Really, connecting is not such a big deal, we jus tdon't want them to be able to change anything.)
How would you deal with this?
Hi Brandon
I don't think you can stop a user connecting to a K2 environment, however you can control what they can do using the SmartObject Administration in the K2 Workspace.
In the specific scenario where a SmartObject connects to a SQL server using a service account so that 8,000+ accounts don't need created in the database, how are developers prevented from executing a read or list method of the SmartObject in a production environment?
This is important because we are considering having sensitive data in the SQL server. It appears that there are only permissions related to publish and delete of SmartObjects and no execute permission setting.
Hi Wabbit
The issue you describe is not unique to K2. When developing an application against a database with sensitive info with any software platform you will face the same issue with giving developers access to the data (either directly or through a single "app" account).
Some suggestions:
Someone will always have the "keys" to the prod database, you just need to manage (and trust) who they are.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.