Hello Community,
I am seeking to create a secure design environment for our K2 Five Citizen Developers. To do this I want to create a seperate and secure Web Application and then only allow users to CD's to develop in that environment. (I know the best solution would be to create a seperate and secure development farm but unfortunately this simply isn't possible). Is it technically feasible to isoltae use of K2 Five tools to one seperate and secure Web Application?
Thanks!
Tom
Best answer by DavidL1
Tom,
While I belive it is possible to create a seperate web app I think there is an easier way. Check out the Authorization Framework that was added to Five.
From the management site, you can set runtime and designtime permissions of folders and objects. You could create a top-level folder for all citizen developers and give them design permissions. Like in SharePoint lower-level objects inherit from those above by default. For regular IT projects deny citizen developers designtime permission. They will only be able to use design tools on the folders where they have been granted permission.
David
+11Tom,
While I belive it is possible to create a seperate web app I think there is an easier way. Check out the Authorization Framework that was added to Five.
From the management site, you can set runtime and designtime permissions of folders and objects. You could create a top-level folder for all citizen developers and give them design permissions. Like in SharePoint lower-level objects inherit from those above by default. For regular IT projects deny citizen developers designtime permission. They will only be able to use design tools on the folders where they have been granted permission.
David
@DavidL
That's very good advice and very helpful, but part of my concern is keeping them from developing against their production data, so while in the Authorization Framework I see the ability to control all K2 Objects, Tools and Capabilities, I'm not seeing how to prevent users from binding their Forms, Views, SmartObjects, and Workflows to their real world data without restricitng the use of K2 development tools to a protected environment.
My thought is to let them have restricted access to a seperate and secure environment, build their solutions, with all necessary K2 security provided through the Authorization Framework, and then hand their deployment packages over to administrators who can deploy them to the production environment. Your thoughts?
Thanks!
Tom
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.