Associating inbound IDs with secondary IDs
Your decisions on password encryption and ID translation determine the value that you use for the primary authorization ID on an attachment request.
About this task
They also determine whether those requests are next treated as connection requests or as sign-on requests. That means that the remote request next goes through the same processing as a local request, and that you have the opportunity to associate the primary ID with a list of secondary IDs in the same way you do for local requests.
Parent topic: Managing inbound SNA-based connection requests