Displaying 4 results from an estimated 4 matches for "realusernam".
Did you mean:
realusername
2017 Oct 25
0
authenticate as userA, but get authorization to user userB's account
...s) of the group user
The pam_groupuser.so module must be referred two times in the PAM
configuration for the given service/resources, i.e.
auth required pam_groupuser.so
<all normal auth modules>
auth required pam_groupuser.so second-pass
The users must use the username "groupusername*realusername" and the
password belonging to "realusername". The first call to pam_groupusers.so
sets the username for PAM to "realusername", so the authentication modules
will use the real username for authentication. The second call to
pam_groupusers.so sets the username for PAM to &q...
2017 Oct 25
2
authenticate as userA, but get authorization to user userB's account
...f at wigner.mta.hu> (Mi 25 Okt 2017 13:28:22 CEST):
> > sales at example.com, using the credentials of the very own account (say
> > hans at example.com)?
>
> We faced the same problem and solved it with a PAM module:
?
> The users must use the username "groupusername*realusername" and the
Yes, this follows the maser-user idea. Great.
I'm curious if the master user mechanism isn't usable.
Maybe it is, I'll check this.
> - dovecot POP/IMAP server
> - vsfptd FTP server
>
> Addendum: for dovecot, add "*" to the allowed username chars t...
2017 Oct 25
6
authenticate as userA, but get authorization to user userB's account
Hello,
given a small organization. There are *personal* mailboxes (mailbox per
user, incl. subfolders et cetera). The users can share specic folders
via the ACL (we call it "other users/", Dovecot calls it "shared"
folder. Additionally there are mailboxes Dovecot calls "public" (we use
the term "groups/"). They are not associated with a specific account,
2017 Oct 25
0
authenticate as userA, but get authorization to user userB's account
...Okt 2017 13:28:22 CEST):
> > > sales at example.com, using the credentials of the very own account (say
> > > hans at example.com)?
> >
> > We faced the same problem and solved it with a PAM module:
> ?
> > The users must use the username "groupusername*realusername" and the
>
> Yes, this follows the maser-user idea. Great. I'm curious if the master
> user mechanism isn't usable. Maybe it is, I'll check this.
The master users are allowed to impersonate anyone and at the same time
cannot login as themselves. Those were the issues...