setup.xqy evals with hardwired security database name

[sparnell]

Several evals in this module contain:
{xdmp:database("Security")}
which fails if the 'Security' isn't the right database (or doesn't exist)

[grtjn]

You could patch $default-security at the top of setup.xqy, but some elem or attr, or maybe even a property in build.properties would be much nicer..

[dmcassel]

Having a default value overridable with a property makes sense. I don't expect this would be used very often, so the default is important, but it makes sense to let someone change it where desired. Shouldn't be hard, I can take this one.

[dmcassel]

The desired security database will need to be expressed in ml-config.xml somewhere. My guess is that whatever security database is specified for the content database should also be used for the modules database. @sparnell, does that sound like a reasonable assumption?

[grtjn]

I believe there already is a feature to choose a sec db per database, but it doesnt get applied. There is a comment that says too dangerous..

If it supposed to be generic, then a generic place would make more sense to me. @default-security on top level elem? With overrides on group (new), server or db..

[dmcassel]

Okay, this is more involved than I thought, and I don't have time to finish it now. I'll come back to this at some point if I can.

[grtjn]

There are no references to "Security" any more in setup.xqy, except for $default-security. I'm still trying to find a good reason to want to change the Security db. Engineering is highly recommending AGAINST doing so.

Considering closing this ticket..