APAR status
Closed as program error.
Error description
JAAS entry WSRRLogin does not work when using a prefix
Local fix
Problem summary
Secure promotion from a cluster using a prefix fails with the following message: com.ibm.sr.governance.api.ServiceRegistryPromotionImpl doLogin javax.security.auth.login.LoginException: No LoginModules configured for WSRRLogin
Problem conclusion
When using WSRR in a cluster with a prefix the JAAS login module was defined as <prefix>WSRRLogin. This has now been corrected to WSRRLogin. This APAR is targeted at WSRR v7.5.0.3.
Temporary fix
Add the missing required JAAS login module back in: This is done through the WAS admin console: Security -> Global security -> Java Authentication and Authorization Service -> Application logins A new entry should be added with the following settings: Alias: WSRRLogin New Login Module with a class name: com.ibm.ws.security.common.auth.module.WSLoginModuleImpl Authentication strategy: REQUIRED Custom property 1: use_appcontext_callback value:true Custom property 2: use_realm_callback value:true
Comments
APAR Information
APAR number
IV10243
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-07
Closed date
2011-12-28
Last modified date
2012-09-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
05 September 2012