Unix Id from Window Login ID


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Unix Id from Window Login ID
# 1  
Old 10-14-2008
Question Unix Id from Window Login ID

Hello All,

My Problem is -> How can we get UNIX id from open mail authentication (Windows ID) in UNIX.

In following command we are using domain name, which may change in your reference.

As, if we use following command.
ypcat passwd | grep rohitp | cut -d: -f5 | cut -d, -f1
=> we get Windows Login ID of rohitp
Rohit Pandey

NOTE : "passwd" is domain name

But if we reverse this
ypcat passwd | grep "Rohit Pandey" | cut -d: -f 1

=> we get multiple UNIX id
flashweb
sramweb
ftmtrn21
nvmioweb
ftmweb
rohitp
ndlfweb
smtweb
wits
tcdweb
nvmpmweb
eclweb
nvmweb
Nvmsiweb


Reason behind multiple UNIX ID is, there may be multiple UNIX ID, whose owner is Rohit Pandey. But there may be specific ID which ownership only to Rohit Pandey. As in above example, ownership of nvmweb ID to multiple user but rohitp only belong to Rohit Pandey


So how i get this rohitp from this list or using other set of command. don't want to use pattern matching kind of command beacuse we don't have any idea about Windows Login Name n UNIX ID .


Regards
Rohit
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

File Transfer from Window server to UNIX and UNIX to UNIX

Dear All, Can someone help to command or program to transfer the file from windows to Unix server and from one unix server to another Unix server in secure way. I would request no samba client. (4 Replies)
Discussion started by: yadavricky
4 Replies

2. Solaris

Position of Login Window...

Greetings! I'm new here and excited to get aquianted with this site! Seems like a good source of knowledge! Anyways, my first problem de'jour deals with the following.... We have dual monitors(top/bottom) for our system. The problem is that the solaris login window is split between the top... (7 Replies)
Discussion started by: ruberked
7 Replies

3. Solaris

Configuring xSun for automatic remote login window

Hey folks, I wish every one is just great. I got to do this: I'm trying to configure my Solaris 10 clients to Automatically Show the login windows of the Main Server whenever the Client restarts or a user logs out. By other means, the Client user don't have to Go to Options->Remote-Login->... (5 Replies)
Discussion started by: ua-agent
5 Replies

4. UNIX Desktop Questions & Answers

only root can login through X window

Dear Friends I'm using Hp-unix release b.11.11 and i'm facing a problem to login through telnet session. i can login only by user root but other users can not login. but if i use x window application like (reflection X) all users can login with no problem. please kindly advice me on how to... (0 Replies)
Discussion started by: hai_jab
0 Replies

5. Solaris

ioctl() fails to get window size from console login

Hi, I need to get the console window size for an application, for which I used ioctl() by passing the TIOCGWINSZ parameter. The ioctl() function does not fail (returns non zero), but it could not get the window size (gets 0x0). When I tried to verify the window size by the stty -a command, the... (2 Replies)
Discussion started by: diganta
2 Replies

6. UNIX for Dummies Questions & Answers

unix window

i recently install redhat linux as a dual boot with win2000. after i log in my unix account. i tried to get window unix by typing startx or xinit. both gave me error. display message among other thing was something like fatal error. any help? thanks (12 Replies)
Discussion started by: bb00y
12 Replies

7. UNIX for Dummies Questions & Answers

Window and Chat for UNIX

Hi i am new to Unix and i was wondering if you could help me with 2 problems i have? Firstly i use Telnet to connect to my main server unix-shells.com and i want to know how i can use the "window" program? i understand how it works but i want to be able to easily make new windows and hide the... (1 Reply)
Discussion started by: ditoa
1 Replies
Login or Register to Ask a Question
pam_hpsec(5)							File Formats Manual						      pam_hpsec(5)

NAME
pam_hpsec - extended authentication, account, password, and session service module for HP-UX SYNOPSIS
DESCRIPTION
The service module implements extensions specific to HP-UX for authentication, account management, password management, and session manage- ment. The use of is recommended for all services, and is mandatory for some services such as and Application writers and system administrators may decide that it is inappropriate to use for some specific applications. When the module is present on the stack, it must be on the top of the stack, above other modules such as or This module is specific to HP-UX, and the functionality may vary significantly between releases. For an interpretation of the module path, please refer to the related information in pam.conf(4). Options The following options may be passed to the service module for all the components: syslog(3C) debugging information at Turns off warning messages. With this option, returns upon success. Without this option, the module returns upon success (which simplifies the PAM configuration). Authentication Component The authentication component provides management of credentials specific to HP-UX. In the future, this component may also implement addi- tional HP-UX specific authentication restrictions in addition to the credential management. Currently, this component initializes audit attributes for the session. In addition to the options listed in the section, the following options may also be passed to the module for authentication. With this option, does not initialize audit attributes for the session. This option is supported solely to maintain su(1) backward compat- ible behavior when is configured with su(1). HP recommends that this option not be applied to other services. With this option, ignores the restrictions or features that this module would otherwise enforce. Note that other common UNIX credentials such as and supplemental group membership are not managed by any PAM module. The application per- forming the authentication is expected to grant these credentials (these credentials must be granted after calling pam_open_session(3)) using the setuid(2) and initgroups(3C) types of calls. Account Management Component This component implements the and restrictions described in security(4). In addition to the options listed in the section, the following options may also be passed to the module for account management. With this option, ignores the restriction. With this option, ignores the restriction. This option is available only if the HP-UX Compartment Login product is installed, and its compartment login feature is enabled. With the option, ignores the compartment login access check restrictions. is defined in the compartment configuration file. Refer to compartment_login(5) for more information about HP-UX Compartment Login. With this option, ignores the restrictions or features that this module would otherwise enforce. Password Management Component This component unconditionally succeeds. Session Management Component This component implements many miscellaneous restrictions such as and documented in security(4). In addition to the options listed in the section, the following options may also be passed to the module for session management. With this option, ignores the setting. With this option, ignores the setting. With this option, ignores the setting. With this option, ignores the setting. With this option, ignores the restrictions or features that this module would otherwise enforce. EXAMPLES
The following is an example of stacking using the module: login session required pam_hpsec.so.1 login session sufficient pam_unix.so.1 login session sufficient pam_ldap.so.1 login session sufficient pam_krb5.so.1 The above rules state that the login's session management requires at least any one of UNIX, LDAP, and Kerberos PAM modules in addition to AUTHOR
was developed by HP. SEE ALSO
pam(3), pam_acct_mgmt(3), pam_authenticate(3), pam_open_session(3), pam_setcred(3), pam.conf(4), security(4), userdb(4), compart- ment_login(5). pam_hpsec(5)