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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
IBM to allow IBM Download Director to explicitly support NTLMv2 as an authentication method
At our bank, usually we download patches for our iSeries servers from IBM Fix Central website using FTP non-secured. But recently IBM stopped supporting anonymous/unsecure FTP clients and allows only Secure FTP (SFTP). Unfortunately, we are not able use this function since ANZ network doesn’t allow to reach the IBM site with SFTP. Our team has been downloading patches from IBM fix central website for years together – recently this change from IBM has put us into trouble in downloading PTFs that resulted us to face compliance issues as well. We tried to use one of the downloading options “IBM Download Director”. But it didn’t work since it does not support NTLM V2 authentication for the proxy servers. To overcome this issue, we got in touch with our account manager from IBM for helping us to have the NTLM V2 authentication. The part of the response from the IBM account manager is below. “As you can see, there are a number of different options available, but I understand that ANZ's preferred option to obtain fixes and patches is via HTTPs through their proxy servers. The proxies use NTLMv2 protocol for authentication, so any method to transfer via HTTPs must implicity or explicity support this method e.g. if IBM Download Director is used, it must support authentication via NTLMv2 (which it does not currently).
So, I think the best path forward - and this is my suggestion only - is to request an enhancement to IBM Download Director to explicitly support NTLMv2 as an authentication method, so that it can be then used to download any IBM fixes via Download Director (which uses multiple HTTPs streams). If you can raise an RFE to request this - or if you have some other ANZ-supported method in mind - then I will try to get a call set up with the right development support folks to get us all on the same page.
Ian Nash Client Technical Architect IBM Systems
IBM Australia, 60 City Road, Southbank, VIC Office: +613-9626-6923 Mobile: 0401 717 460”
Also we got in touch with one of the architects in the IBM Electronic Support area to ask what other options can be made available - noting works for ANZ restrictions around using SFTP/FTPS secure transfer methods, and only acceptable option is to use an HTTPs method via a proxy server with NTLM v2 authentication. Current download director doesn’t support NTLM v2 authentication. We need this urgently for us to download patches from IBM website and deal with compliance/audit.
Trying to download PTFs but we are not able to download.
Do not place IBM confidential, company confidential, or personal information into any field.