AT7~AIX6-1 & Future LDAP

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Pete:

A) we presently use nailed telnets to take 
a user from a desktop icon via the SAME SOCKET tied to the PICK PROCESS.
So 
an AT session with socket# 3101 would end up on process 101 @ the D3 "enter your 
user ID:" prompt.

issues... each PC/Desktop has to have the unique SOCKET 
NUMBER... roughly 300 PCs... and growing.  There are conflicts with the 3000 range on Aix 6.1
===>

B) CITRIX users utilizes ssh, 
secure_keys, and AT script to enter the user "eprise" .profile of "eprise" 
starts the usr at the next available Pick Process starting at 830  (defined 
serialrange in Pick0)

#cat 
.profile

PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:.
export 
PATH
if [ -s "$MAIL" ]           # This is at Shell startup.  In 
normal
then echo "$MAILMSG"        # operation, the Shell checks
fi 
                         # periodically.
# ABEST WMS 12/23/09  bring over 
script from Aphrodite
# PRODUCTION COMMAND!
# 4th pass remove "-l" that 
carries users permissions!!!
d3 -dcdon -d '\r'
# ABEST WMS 18dec09 Pete 
Schellenbach LOGOFF anyone dropping back down to 
AIX
exit
exit
===>

C) Speculating about NEW 
alternative.

1) AT would connect via ssh * (default socket) (secure_keys) or (CARRY USERNAME) 
to AIX user "d3ports"  whose .profile script would:

A) execute a 
"d3tcl" command that would login to D3 and return the PICK PROCESSES  that 
were defined in the users file.  For instance returning  ["username" 101] 
(NEED TO ALLOW for MULTIPLE SESSIONS)
then

d3 101 username.arg -dcdon 
  *** would put them on Pick Process 101. Can probably pass the user_name & 
maybe password.  ****

PROS/CONS:  user process is nailed, but will get 
the next socket avail on AIX.  NO RELATIONSHIP WITH PICK PROCESS & SOCKET 
#.

Other:

1) D3-9.1 will support LDAP.  NOT ONLY LOGINS. but 
hopefully maintenance as well.
2) D3-9.1 will have Pick "nailed ssh"
3) 
D3-9.x allows (2) connects on (1) NIC using a SINGLE License.
4) Boss
wants a single "user maintenance across all systems"  no unique socket 
numbers.
5) MIS has valid concerns AFTER login with DISCONNECTS, TIMEOUTS 
& SO FORTH.

===>

How about a brief discussion and Walkthru? 
 Other alternatives?

Thank you ~ Mike Shebesta Abest Group 513-943-4425

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MikeAbest Members Profile Find Members Posts Newbie Joined: January 12 2007 Location: United States Status: Offline Points: 2	Post Options Post Reply Quote MikeAbest Report Post Thanks(0) Quote Reply Topic: AT7~AIX6-1 & Future LDAP Posted: May 16 2012 at 5:20am
	Pete: A) we presently use nailed telnets to take a user from a desktop icon via the SAME SOCKET tied to the PICK PROCESS. So an AT session with socket# 3101 would end up on process 101 @ the D3 "enter your user ID:" prompt. issues... each PC/Desktop has to have the unique SOCKET NUMBER... roughly 300 PCs... and growing. There are conflicts with the 3000 range on Aix 6.1 ===> B) CITRIX users utilizes ssh, secure_keys, and AT script to enter the user "eprise" .profile of "eprise" starts the usr at the next available Pick Process starting at 830 (defined serialrange in Pick0) #cat .profile PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:. export PATH if [ -s "$MAIL" ] # This is at Shell startup. In normal then echo "$MAILMSG" # operation, the Shell checks fi # periodically. # ABEST WMS 12/23/09 bring over script from Aphrodite # PRODUCTION COMMAND! # 4th pass remove "-l" that carries users permissions!!! d3 -dcdon -d '\r' # ABEST WMS 18dec09 Pete Schellenbach LOGOFF anyone dropping back down to AIX exit exit ===> C) Speculating about NEW alternative. 1) AT would connect via ssh * (default socket) (secure_keys) or (CARRY USERNAME) to AIX user "d3ports" whose .profile script would: A) execute a "d3tcl" command that would login to D3 and return the PICK PROCESSES that were defined in the users file. For instance returning ["username" 101] (NEED TO ALLOW for MULTIPLE SESSIONS) then d3 101 username.arg -dcdon * would put them on Pick Process 101. Can probably pass the user_name & maybe password. ** PROS/CONS: user process is nailed, but will get the next socket avail on AIX. NO RELATIONSHIP WITH PICK PROCESS & SOCKET #. Other: 1) D3-9.1 will support LDAP. NOT ONLY LOGINS. but hopefully maintenance as well. 2) D3-9.1 will have Pick "nailed ssh" 3) D3-9.x allows (2) connects on (1) NIC using a SINGLE License. 4) Boss wants a single "user maintenance across all systems" no unique socket numbers. 5) MIS has valid concerns AFTER login with DISCONNECTS, TIMEOUTS & SO FORTH. ===> How about a brief discussion and Walkthru? Other alternatives? Thank you ~ Mike Shebesta Abest Group 513-943-4425

NEFURNMART Members Profile Find Members Posts Newbie Joined: May 24 2011 Location: United States Status: Offline Points: 25	Post Options Post Reply Quote NEFURNMART Report Post Thanks(0) Quote Reply Posted: January 08 2014 at 9:48am
	Mike: We also are very dependent on nailed Pick ports in our environment and have accomplished port mapping using three different methods: Method one, which is useful with clients that use static IP addresses, is to just create a cross reference map between the IPs and the Pick ports. Host script pops IP address from SSH_ENVIRONMENT variable and just have to look up in map to get corresponding Pick port. Method two, which we began using as we started migrating towards DHCP addresses was to spoof the HostTermType setting in the AT session record to pass a DHCP flag with the Pick port number as well as the terminal type -- ie DHCP-101-wyse60. Host script can then intercept, parse and reset host term type. Method three, which we began using with web clients that are using ATIE and don't have a unique client session record is to perform a Windows machine name lookup using VB interface in AT, and cross reference the machine name to a fixed Pick port. All three methods work well and host script easily establishes proper port mapping regardless of method. (Unfortunately, also gives more life to those darn nailed ports!) -D