Enrique Vega wrote:
> id uid gid sitegroup
> | 1| �1| �0| 1
> | 2| �2| �1| 1
> ------------------------------
>
> id 1, which is the default admin does not work.
Correct. Root users must be in gid 0 and in SG0.
> id 2 now works as an administrator.
For the specific sitegroups I'd expect.
> What I've noticed is that the gid of uid 1 is set to 0 and
> that there does not seem to be any midgard - table grp 0. Did I delete it in
> the process of trying to get things to work, or what?
Nope. Group 0 and SG 0 do not really exist but have special meaning.
In a non-SG environment, members of group 0 have full control. In a SG
environment these users must also be in SG0.
> The reason for my concern is everything I've read about gid 0 is that it is
> the admin root. Does this still apply now that everything has been adjusted
> to use sitegroup 1?
No. GID0/SG0 makes you root. SG admins must be in the SG they're to be
admins of, the group record must be in that SG, their member record
must be in that SG, and the 'admingroup' field of the SG record must
be set to the id of that group.
> > if you have member(uid, 0, 0) that makes that uid root. _Do not_ use gid 0
> > unless you want to create a root user.
>
> Is this true now that everything has a sitegroup of 1? If not, could someone
> please tell me which settings I should be looking at for the admin root?
UPDATE person SET sitegroup=0 WHERE id=1;
in your case.
> Or if my new uid 2 with gid 1 and sitegroup 1 is the correct one to use as
> admin?
Set up a group, membership record and sitegroup record as outlined
above.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
