This is an IBM Automation portal for Cloud Platform products. 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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Allow useAuthenticationDataForUnprotectedResource being set at application level
This idea comes from case . z/OSMF has multiple http endpoints. One endpoint needs to set useAuthenticationDataForUnprotectedResource to False while while other endpoints need to set useAuthenticationDataForUnprotectedResource to True. Liberty doesn’t support useAuthenticationDataForUnprotectedResource being set at the application level.
More information about the background -
Customer has an environment that has set the max number of wrong password attempts to 5 times. Customer reported their user account got revoked after 3 failed attempts when authenticating with z/OSMF with a wrong/expired password. This is because the password was checked twice every time when customer authenticate with z/OSMF. One time with Liberty, one time with z/OSMF with method javax.servlet.http.HttpServletRequest.login() because z/OSMF need to call the method to inform the user detailed failure for example password expire or user revoke. IBM service suggested we set useAuthenticationDataForUnprotectedResource to False, which did fix this particular issue. However, as useAuthenticationDataForUnprotectedResource is effectively globally, other endpoints do require useAuthenticationDataForUnprotectedResource to be set True.
Do not place IBM confidential, company confidential, or personal information into any field.