Hi Harry,

To some extend it certainly does. But the best argument against doing so is 
probably that MarkLogic Server's security layer doesn't cater this. You could 
obviously create a security function yourself, with priv's and roles and all, 
but as pointed out, you could lose all your custom properties on user level at 
next upgrade.

Using description field gives the benefit you can still use the Admin interface 
to create users, which is not possible with 2 and 3. But option 2 is doable as 
well with a little bit of abstraction. Just create a few functions that take 
care of user management, and take care of keeping security and your extension 
xml in synch. Makes sense to put such functionality in a separate module 
anyhow..

Kind regards,
Geert

Van: general-boun...@developer.marklogic.com 
[mailto:general-boun...@developer.marklogic.com] Namens Harry B.
Verzonden: donderdag 29 september 2011 3:28
Aan: General MarkLogic Developer Discussion
Onderwerp: Re: [MarkLogic Dev General] Adding custom properties\attributes to 
users


I am surprised there's no additional input on this issue.

Since the user info in the security database is just an xml file, it stands to 
reason we could safely add properties to them, no?
On Sep 27, 2011 1:20 PM, "seme...@hotmail.com<mailto:seme...@hotmail.com>" 
<seme...@hotmail.com<mailto:seme...@hotmail.com>> wrote:
>
> If we want to add custom properties or attributes to a user account in 
> MarkLogic (beyond username and description), it seems like we have the 
> following options:
>
> 1. Put the values in the description field tokenized (Bob | Accounting | 
> 555-1223 | b...@mail.com<mailto:b...@mail.com>)
> 2. Use a separate XML file in the content database
> 3. Add properties to the XML file for the user in the Security DB
>
> #1 is good except there is a limit to the number of characters. #2 adds the 
> overhead of making sure the Securty DB and "extended user info" XML files in 
> the content DB are always in sync. #3 starts tinkering with the Security DB 
> which sounds like something to avoid.
>
> I'm hoping there are other options. What do you all recommend?
>
> thanks,
> Ryan
>
>
_______________________________________________
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to