This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Declining this as requested since existing options suffice.
Yes - those do solve my problem.
While I would prefer an encrypted password, this should suffice for my scenario. Perhaps I can secure the netrc file so other users can not view it.
Lets close out this request.
In order to automatically login in to a 5250 session, you must be using either bypass signon or kerberos. The replacement product IBM i Access Client Solutions (ACS) supports both. I'm guessing you are using bypass signon. While ACS currently does not capture the Windows user id and password, there are a couple ways you can pass the user id and password to ACS without the user getting prompted. (1) Using the command line /plugin=logon. See section 9.1.8 in the GettingStarted document. (2) ACS also supports a netrc file. See section 9.11 in the GettingStarted document.
You mentioned that you "have computers on the shop floor that auto login to Windows". That process should be able to leverage either one of these options to allow bypass signon to continue as you have it today.
If neither of these options will work, please provide specific details of your auto login process and whether you are using bypass signon or kerberos.
I would recommend looking at Single Sign On solutions.
Hi,
this can be accomplished with SSO.
BR+