PI56589: USER/GROUP MAPPING TO A SECURITY ROLE FAILS FOR EBA APPLICATION IF IT BELONGS TO A USER REGISTRY CONFIGURED IN SECURITY DOMAIN

Fixes are available

APAR status

Closed as program error.

Error description

We can map user and group to a security role even if it is EBA
application.

In admin console, we can see the setting at Business-level
applications > BLA_NAME >  EBA_NAME > Security role to user or
group mapping page.

If the group or user belongs to a user registry of a security
domain, the mapping fails with CWSAL0041E (The specified
user(or group) XXXX is not valid. Check log for details.)

Here is an example to replicate the issue.
1. create a dmgr profile with WIM repository
2. add a custom profile and create a server
3. add a security domain(& its realm) for the server
4. configure custom registry for the domain.
5. deploy a secure EBA(osgi) application.
6. try to map a group in the custom registry to a role
and confirmed the same issue(CWSAL0042E).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of OSGi  *
*                  applications                                *
****************************************************************
* PROBLEM DESCRIPTION: Mapping roles to users or groups        *
*                      for an OSGi application fails           *
*                      generating CWSAL0041E or CWSAL0042E     *
*                      messages.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When mapping roles to users or groups for an OSGi application
the specified users or groups are automatically validated as
part of the mapping process.  This validation does not occur
when performing the same mapping for J2EE applications.
The validation process always occurs against the default user
registry.  If the users or groups being validated exist in a
non-default user registry then the validation process fails.

Problem conclusion

The validation process is not necessary and not capable of
validating users and groups against non-default user registries.

A new JVM system property
com.ibm.ws.eba.bla.MapRolesToUsersStep.SkipValidation can be
set to a value of true to disable the validation process when
mapping roles to users or groups for OSGi applications.

In an Network Deployment environment the system property
should be specified on the deployment manager.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.11 and 9.0.0.2. Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI56589
Reported component name
WEBS APP SER DE
Reported component ID
5724H8900
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-03
Closed date
2016-07-01
Last modified date
2016-07-01

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI56589: USER/GROUP MAPPING TO A SECURITY ROLE FAILS FOR EBA APPLICATION IF IT BELONGS TO A USER REGISTRY CONFIGURED IN SECURITY DOMAIN

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?