PI85213: FEDERATED REPOSITORY MAY NOT USE UNIQUEGROUPIDMAPPING OUTPUTPROPERTY WHEN CALLING USERREGISTRY.GETUNIQUEGROU

Fixes are available

APAR status

Closed as program error.

Error description

Federated Repository was using uniqueUserIdMapping
outputProperty instead of the uniqueGroupIdMapping
outputProperty for one code path when
UserRegistry.getUniqueGroupId() was called. The error occurs
in
calls to WIMUserRegistry.getUniqueGroupId() which can can be
made when using Federated Repositories by directly calling
the
UserRegistry API or during the normal flow of authentication
and authorization.

The result is that UserRegistry implementations (including
the
basic registry, and custom user registries) may return an
unexpected unique group ID. By default, both the
outputProperty
for uniqueUserIdMapping and uniqueGroupIdMapping is
"uniqueName", so the errant behavior is limited to
configurations where the customer has overridden one of the
two
properties.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty- Virtual Member Manager      *
*                  (VMM)                                       *
****************************************************************
* PROBLEM DESCRIPTION: Federated Repository may not use        *
*                      uniqueGroupidMapping outputProperty     *
*                      when calling                            *
*                      UserRegistry.getUniqueGroupId().        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Federated Repository was using uniqueUserIdMapping
outputProperty instead of the uniqueGroupIdMapping
outputProperty for one code path when
UserRegistry.getUniqueGroupId() was called. The error occurs in
calls to WIMUserRegistry.getUniqueGroupId() which can be made
when using Federated Repositories by directly calling the
UserRegistry API or during the normal flow of authentication and
authorization.

The result is that UserRegistry implementations (including the
basic registry, and custom user registries) may return an
unexpected unique group ID. By default, both the outputProperty
for uniqueUserIdMapping and uniqueGroupIdMapping is
"uniqueName", so the errant behavior is limited to
configurations where the customer has overridden one of the two
properties.

Problem conclusion

The code was updated to use the uniqueGroupIdMapping
outputProperty.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.3.  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
PI85213
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-28
Closed date
2017-09-25
Last modified date
2017-09-25

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

RCD0 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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI85213: FEDERATED REPOSITORY MAY NOT USE UNIQUEGROUPIDMAPPING OUTPUTPROPERTY WHEN CALLING USERREGISTRY.GETUNIQUEGROU

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

RCD0 PSY

Document Information

Share your feedback

Need support?