12-04-2008
you can check this:
# grep "userA" /etc/user_attr
or
after su - userA
#roles
This will provide the roles assigned to this user
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi There,
i need to creat USERS in UNIX with restricted access to different directories.
for example
user1 should have access to dir1 and dir2
user2 should have access to dir2 and dir3
Please help me (4 Replies)
Discussion started by: ramanan25
4 Replies
2. UNIX for Advanced & Expert Users
Hi All!
I would like to know if there is any specific way by which I can restrict access to apecific users (ip addresses).
OS : Red hat linux
Thanks!
nua7 (6 Replies)
Discussion started by: nua7
6 Replies
3. AIX
Hi!
this would be my first time to post here in this forums, hope you can help me with my queries.
i would like to create a different user name but have the same access rights. Example: root > rootbaby.
thanks (5 Replies)
Discussion started by: HPL1706
5 Replies
4. Shell Programming and Scripting
EDIT : This is for perl
@data2 = grep(/$data/, @list_now);
This gives me @data2 as
Printing data2 11 testzone1 running /zones/testzone1 ***-*****-****-*****-***** native shared
But I really cant access data2 by its individual elements.
$data2 is the entire list, while $data,2,3...... (1 Reply)
Discussion started by: shriyer
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I want to access another users files and directories.Is there any command to do in unix ??.I think CHOWN would work.May i know the exact command for it.
Regards, (1 Reply)
Discussion started by: William1482
1 Replies
6. UNIX for Dummies Questions & Answers
hi all,
i want to know y kernel is giving access for multiple users to access a file when one user may be the owner is executing that file. Because other user can manipulate that file when the other user is executing that file, it will give the unexpected result to owner . plz help me... (1 Reply)
Discussion started by: jimmyuk
1 Replies
7. HP-UX
Hp info
HP-UX tmelps04 B.11.31 U ia64
issue I created a user in his primary group is sysadmin. However when this user executes HPPI he gets shot down because he is not a super user. How do I grant the user permissions to access the beroot script?
Sorry, user xxxxxx is not allowed to execute... (2 Replies)
Discussion started by: sctxms
2 Replies
8. Shell Programming and Scripting
Hi,
I would like to retrieve a list of user ids on an AIX server along with the access rights that each id has? Can someone please help me on how this can be achieved?
Gayathri (3 Replies)
Discussion started by: ggayathri
3 Replies
9. Solaris
Hi All,
I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration.
Regards,
Sahil (1 Reply)
Discussion started by: sahil_shine
1 Replies
10. Solaris
Hi,
I always use "sudo -U user -l" as root and it gives me list of sudo access, that person have. But on one Solaris server, I can't run it. recently only I installed latest patchset on this server. Not sure, if that changed something on this. However, sudo package is showing old one.
# id -a... (1 Reply)
Discussion started by: ron323232
1 Replies
roles(1) User Commands roles(1)
NAME
roles - print roles granted to a user
SYNOPSIS
roles [ user ...]
DESCRIPTION
The command roles prints on standard output the roles that you or the optionally-specified user have been granted. Roles are special
accounts that correspond to a functional responsibility rather than to an actual person (referred to as a normal user).
Each user may have zero or more roles. Roles have most of the attributes of normal users and are identified like normal users in passwd(4)
and shadow(4). Each role must have an entry in the user_attr(4) file that identifies it as a role. Roles can have their own authorizations
and profiles. See auths(1) and profiles(1).
Roles are not allowed to log into a system as a primary user. Instead, a user must log in as him-- or herself and assume the role. The
actions of a role are attributable to the normal user. When auditing is enabled, the audited events of the role contain the audit ID of the
original user who assumed the role.
A role may not assume itself or any other role. Roles are not hierarchical. However, rights profiles (see prof_attr(4)) are hierarchical
and can be used to achieve the same effect as hierarchical roles.
Roles must have valid passwords and one of the shells that interprets profiles: either pfcsh, pfksh, or pfsh. See pfexec(1).
Role assumption may be performed using su(1M), rlogin(1), or some other service that supports the PAM_RUSER variable. Successful assumption
requires knowledge of the role's password and membership in the role. Role assignments are specified in user_attr(4).
EXAMPLES
Example 1: Sample output
The output of the roles command has the following form:
example% roles tester01 tester02
tester01 : admin
tester02 : secadmin, root
example%
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/etc/user_attr
/etc/security/auth_attr
/etc/security/prof_attr
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
auths(1), pfexec(1), profiles(1), rlogin(1), su(1M), getauusernam(3BSM), auth_attr(4), passwd(4), prof_attr(4), shadow(4), user_attr(4),
attributes(5)
SunOS 5.10 14 Feb 2001 roles(1)