search for: primarygidnumb

...ich is true > for UID and wrong for GID which is not reflecting gidNumber configured > into AD. Ah, that is because you think that giving a user a gidNumber, this becomes the users main GID, it doesn't. The users primary gid number is obtained from what is set in the aptly named 'PrimaryGidNumber' attribute, AD obtains this and then uses whatever gidNumber that groups object contains. Should I speak again about home dir ? Shell ? Gecos ? login attribute ?... No, because I have already dealt with that. > > SSSD grant sys admin possibility to chose all that, forging users as...

...e context of AD *YES*, in AD, every users primary group is 'Domain Users' and there is no concept of a private group. You control access by using NTFS ACLs, either by setting these from windows or with 'setfacl'. To change a users primary group, you will need to change the users PrimaryGidNumber attribute to contain the RID of the new group, it is possible but has to be done in a certain way. I would not suggest doing this, windows expects every user to be a member of 'Domain Users'. > > >> >> to set up home directory to unixHomeDirectory or to homeDirectory...

...; UID and wrong for GID which is not reflecting gidNumber configured into AD. >> > > Ah, that is because you think that giving a user a gidNumber, this becomes > the users main GID, it doesn't. The users primary gid number is obtained > from what is set in the aptly named 'PrimaryGidNumber' attribute, AD > obtains this and then uses whatever gidNumber that groups object contains. False. In system point of view user primary group is the one declared in user line (the equivalent of line from /etc/passwd) and this can be changed using "sg" command for example. And...

...gt;>> 'Domain Users' and there is no concept of a private group. You control >>>> access by using NTFS ACLs, either by setting these from windows or with >>>> 'setfacl'. To change a users primary group, you will need to change the >>>> users PrimaryGidNumber attribute to contain the RID of the new group, it >>>> is >>>> possible but has to be done in a certain way. I would not suggest doing >>>> this, windows expects every user to be a member of 'Domain Users'. >>>> >>>> >>>...

...y group is >>> 'Domain Users' and there is no concept of a private group. You control >>> access by using NTFS ACLs, either by setting these from windows or with >>> 'setfacl'. To change a users primary group, you will need to change the >>> users PrimaryGidNumber attribute to contain the RID of the new group, it >>> is >>> possible but has to be done in a certain way. I would not suggest doing >>> this, windows expects every user to be a member of 'Domain Users'. >>> >>> >>> Sorry, but that'...

...UID and wrong for GID which is not reflecting gidNumber configured > > into AD. > > Ah, that is because you think that giving a user a gidNumber, this > becomes the users main GID, it doesn't. The users primary gid number is > obtained from what is set in the aptly named 'PrimaryGidNumber' > attribute, AD obtains this and then uses whatever gidNumber that groups > object contains. > > > Should I speak again about home dir ? Shell ? Gecos ? login attribute ?... > > No, because I have already dealt with that. > > > > > SSSD grant sys admin...

On 19/10/15 16:46, mathias dufresne wrote: > AD from Samba or Microsoft is mainly a database for storing users (and > associated stuffs). It comes also with stuffs (protocols) to connect and > retrieve information. > > How the client uses these information is, as always, a choice from that > specific client. > > Your AD client is your Squid/Squidguard(ian) server. Its job