Problem Note 34117: Invalid or missing credentials in the JAAS-J2C Authentication configuration for WebSphere might cause probems in WebSphere and SAS® BI Dashboard
 |  |  |  |
Invalid or missing credentials in the JAAS-J2C Authentication configuration for WebSphere might cause probems in WebSphere and SAS BI Dashboard.
The following symptoms might appear:
- SAS BI Dashboard stops responding if you try to save a newly created indicator.
- A NullPointerException appears in the WebSphere log. (Note: Because of the length of the message, the text is at the end of this note.)
The root of the problem involves missing or invalid configuration of the JAAS-J2C Authentication Alias in the WebSphere admin console. WebSphere does not support SAS encoded or encrypted password values in this context.
To access the settings for the credentials in the WebSphere administrative console, click Resources ► JDBC ► Data sources ► SharedServices ► JAAS ► J2C authentication data ► SASAppSrv01Node/SASJAAS.
Documentation to guide you in correcting the setting with the proper values can be found in "Passwords That Are Managed By the SAS Deployment Manager" under the section "Additional Managed Passwords in the Web Environment".
The following exception text might appear as a symptom of this problem:
An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource sas/jdbc/SharedServices : java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at java.util.Properties.setProperty(Properties.java:128) at com.ibm.ejs.j2c.J2CUtilityClass.createMCFEntry(J2CUtilityClass.java:381) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandPM(ConnectionFactoryBuilderServerImpl.java:551) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObjectInstance(ConnectionFactoryBuilderServerImpl.java:922) at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:608) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:705) at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:2093) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1947) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:149) at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:144) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896) at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191) at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:406) at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:384) at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:204) at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:144) at javax.naming.InitialContext.lookup(InitialContext.java:351)
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | IBM WebSphere Application Server | 64-bit Enabled Solaris | 6.1 | 6.1 | 9.2 TS2M0 | 9.2 TS2M0 |
When this problem occurs the only error may be a NullPointerException in the WebSphere log. A possible symptom is SAS BI Dashboard hanging when trying to save a newly created indicator.
It is due to invalid or missing credentials in the JAAS - J2C Authentication configuration for WebSphere.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2008-12-10 11:12:40 |
| Date Created: | 2008-12-04 09:37:36 |