Home
TeamSite
TeamSite, LiveSite and OpenDeploy
LDAP user alternative file update methods
System
Hey DevNetters -
We're planning an upgrade from our current 6.7.1 (no service pack) Solaris installation.
One of the big changes we're looking at is migrating from OS-based users to LDAP / Active Directory users. We've got this working in 6.7.1 SP1 on our Development server.
This is working nicely in some regards; we can search and choose new users from our AD system, their email addresses are automatically populated and, a bonus, they can now use their AD domain passwords to sign into TeamSite. All good improvements.
Then I start to look at what these non-OS users **can't** do and it gets more complex. For instance, I no longer can see from the server command line (using ls -la, for instance) who updated a particular file. OK, I can understand that.
But here's the tough one: LDAP users can't use samba and can't use ftp either, as far as I can tell. So the folks who we're able to set up a Windows shortcut 'dropbox' to occasionally add files can no longer do that. Developers who map a Windows / samba shortcut to a TeamSite branch area as an app server doc root may lose that capability. And, they no longer can set up their ftp client and easily transfer contents into a workarea that way - which is an easy method to work with Dreamweaver in conjunction with TeamSite.
Granted, these other update methods bypass the TeamSite locking mechanisms (maybe not always a bad thing...), but they're also what allows the system to be used in a faster and more flexible manner.
Given all that leadup, here's a question: can LDAP based users only update TeamSite with external content by using the ContentCenter 'import' function?
Thanks as always,
Wally Box
Nike, Inc.
Find more posts tagged with
Comments
There are no comments yet