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).
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.
See this idea on ideas.ibm.com
After a user is authenticated, there are still checks against the server's guest id to the EJBROLE profiles. This can cause, in some cases, excessive logging of unexpected, but valid, failures against the server's guest id and the EJBROLE profiles on larger web applications. Possible shorter code path may to be just check if request has valid authentication method first before checking against the guest id.
Idea priority | Medium |
RFE ID | 150103 |
RFE URL | |
RFE Product | WebSphere Application Server |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Upon analysis we believe that the problem that triggered this only occurs when using ACF2 as the SAF implementation. When we do the necessary checks we pass LOG=NOFAIL on the check which should suppress any error message. However it appears that ACF2 is ignoring LOG=NOFAIL and logging in any case. Since this is only a problem with ACF2 and the checks need to be performed to maintain security there is no change we can make to Liberty.