Hi Jakob I guess it’s all about giving users choices – even if they’re choices that aren’t used very much.
You could use a separate security database to ensure your application user ids are entirely separate from your admin user ids – not such a bad idea. I admit I’ve never done this myself, though I wouldn’t rule it out. And why can't I view and modify a newly created security database as I can the original one? I’m guessing you mean why can’t I put the admin console on top of ANY security db? You possibly can, by setting up a new appserver with the modules db = Admin folder on filesystem and content db = ‘new’ security db. This would be a ‘try it and see’ option. You can use the sec: calls on any Security db however – and I’ve done this myself when I’ve occasionally had to do ‘creative’ things. If there’s anyone on the list with a hand in the original design, they’d be able to give you the actual reasons. Ken From: [email protected] [mailto:[email protected]] On Behalf Of Jakob Fix Sent: 25 September 2014 14:47 To: General Mark Logic Developer Discussion Subject: [MarkLogic Dev General] security database(s) Hi, so we're wondering why in MarkLogic's management UI you have a dropdown menu to select your security database for a given database. because everybody we've talked to says to use the generic Security db. Why am I given a choice if actually I shouldn't (something to do with clusters)? I know we need several and are currently attempting to recreate new security databases that in turn have as their security database the default one ... And why can't I view and modify a newly created security database as I can the original one? Thanks for enlightening us! cheers, Jakob.
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
