User Management for OpenDeploy

ttriemst

Hello all,

I have a high level question about how best to manage users for OpenDeploy. We have had TeamSite and OpenDeploy installed and running for many years, but have barely leveraged the application. For the most part, we have had one group be responsible for managing and deploying content. We are now in the middle of redesigning our web site, which includes over hauling the business process for the maintaining the web content. We are going to start leveraging TeamSite and OpenDeploy for how it was meant to be used. I have a good understanding of how to use the out of the box user management system shipped with TeamSite (we will use an LDAP database for authentication purposes only), but am struggling with how best to manage the OpenDeploy users. For the initial roll out, we will only have a two or three users promoting content to production. We are anticipating to max out at about 25 users that would potentially deploy content in the future. Would anyone be interested in sharing their best practices for OpenDeploy user management?

Thanks

Adam Stoller

Hello all, I have a high level question about how best to manage users for OpenDeploy. We have had TeamSite and OpenDeploy installed and running for many years, but have barely leveraged the application. For the most part, we have had one group be responsible for managing and deploying content. We are now in the middle of redesigning our web site, which includes over hauling the business process for the maintaining the web content. We are going to start leveraging TeamSite and OpenDeploy for how it was meant to be used. I have a good understanding of how to use the out of the box user management system shipped with TeamSite (we will use an LDAP database for authentication purposes only), but am struggling with how best to manage the OpenDeploy users. For the initial roll out, we will only have a two or three users promoting content to production. We are anticipating to max out at about 25 users that would potentially deploy content in the future. Would anyone be interested in sharing their best practices for OpenDeploy user management? Thanks

First - having attended GearUp this year - one of the themes that Interwoven is striving for in a future release (probably 2009) is more consistency and uniformity across their products - including, but not limited to, user management.

Second, most implementations I've worked on generally have deployments kicked off from a workflow externaltask process, and allow the task to be owned pretty much by anyone (often the job owner, sometimes a generic "TS Master" or "TS Admin" account) - and you either turn off CLT authentication for OD completely, or ensure that all the TS users are OD users and that they all have the ability to run the workflow-based deployment.

If you truly want to restrict the deployment process - you need to carefully control what user owns deployment tasks in the workflow and/or ensure that the proper users are registered as OD-users in OpenDeploy -- however, there's a problem with utilizing the OD Admin GUI - which is (on Windows) that it requires Log On Locally privileges....