Hi,
I have a client who wants to build a web application that would be made accessible to several of their clients. Each of those clients would have an administrator who would log-in to the site and be able to add more users from that client. These clients are very sensitive about their own data, and I am proposing that there would be a separate document database for each. But I am wondering if it is also practical to have a separate security database for each client too? This would help sell the concept of a single server being used for theirs and other's data, as we could say that their documents AND their security details would be separate from other's data (maybe even on a separate drive, for the really paranoid!). It would also be useful because the additional users added be each client administrator could not clash with the names of users from other clients. However, is that a practical model? I would not expect to use the MarkLogic admin interface to create users etc in each security database, but are there too many complications to make this approach practical? I noted the following the adminsitrator's guide"... "However, security objects created through the Admin Interface are stored in the Security database by default. Mark Logic recommends leaving databases connected to Security as their security database." Neil.
_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
