Long user IDs for Client Access v 5R4

15 pts.
Tags:
iSeries User Profiles
iseries v5r4
We are in the process of changing our user IDs on our Windows Servers (Due to centralization) Because of this move our user IDs will be firstname.lastname. How can we set up our client access program so that we can utilize these longer user IDs. Thanks for your help!

Software/Hardware used:
Client Access V5R4

Answer Wiki

Thanks. We'll let you know when a new response is added.

You can’t. You need to set up an LDAP server so you can use single sign-on using enterprise identity mapping. Then you can associate all of your different user id’s together under one main id. Once you log on with that one id, any other log on required will be fed with a token from the LDAP server.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Boss429
    Littlepd, Thank you for your response! Do you know if the user id length has changed with V6R1? Will we have to utilize the LDAP server for this as well?
    15 pointsBadges:
    report
  • Teandy
    Do you know if the user id length has changed with V6R1? The length of the user profile has been 10 characters for as long as I can remember, and I started out on the Sys/38 a little over 20 years ago.
    5,860 pointsBadges:
    report
  • TomLiotta
    Do you know if the user id length has changed with V6R1? The length hasn't changed, nor would I expect it to change in the foreseeable future. Instead, it should become irrelevant, somewhat as noted by Littlepd. If it's necessary to make your iSeries user IDs match up with Windows user IDs, then you should simply go to a "single signon" environment. The issue of matching profiles and matching passwords effectively goes away. An LDAP server is probably already running on your iSeries. You possibly already use network logons (i.e., Active Directory) for your Windows activities. What the basic idea is is to integrate your iSeries connections into the whole structure of Windows connections. When a user logs into your Windows network and is authorized to access your iSeries, it isn't necessary to specify any iSeries user ID at all -- the Windows user ID can allow access to your iSeries just like it can allow access to a Windows file server or any Windows share. You set your Client Access up to use the network authentication as Windows does. No logon window shows up, no user ID needs to be typed by any user -- assuming that you have granted the rights to access your iSeries to that user. You probably realize that I've simplified it all and glossed over all of the details. Regardless, that's essentially how it's intended to work and where IBM has been moving things and why it's unlikely that long user IDs aren't coming any time soon. They simply shouldn't be needed. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following