3198262 - How to remove SAML2LoginModule associated error messages in defaultTrace when authentication is executed against the policy configuration service.naming

You find many SAML2LoginModule associated error messages in defaultTrace like following.
-----------------------------------------------------------------------
#Error#com.sap.security.saml2.sp.SAML2LoginModule#
...
[EXCEPTION]
java.lang.NullPointerException: while trying to invoke the method java.lang.Boolean.booleanValue() of a null object loaded from local variable 'isSecure'
 at com.sap.security.saml2.sp.SAML2LoginModuleUtil.isRequestSecure(SAML2LoginModuleUtil.java:200)
-----------------------------------------------------------------------

And if you collect the TSHW trace or security.log, you can find the authentication is executed against the policy configuration 'service.naming' as same time as the time stamp of the error message in defaultTrace. The authentication detail shows SAML2LoginModule is used like following.
-----------------------------------------------------------------------
Authentication Stack: service.naming
Login Module    
...
com.sap.security.saml2.sp.SAML2LoginModule
...
-----------------------------------------------------------------------

PLEASE NOTE: 
1. TSHW trace can be collected as SAP note 1332726 - Troubleshooting Wizard (Using case "Authentication")
2. security.log can be found in path /usr/sap/<sid>/<INSTANCE id>/j2ee/cluster/serverX/log/system

Netweaver AS Java

KBA , BC-JAS-SEC-LGN , Logon, SSO , BC-JAS-SEC , Security, User Management , How To