IBM Support

LI81728: CHANGING THE MAPPING SETTINGS OF AN OIDC USER REGISTRY IS NOT REFLECTED IN THE UI

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When you create a new OIDC User Registry in API Manager / Cloud
    Manager and change the Mapping settings to map the claims
    differently from the default., the changes do not appear in the
    UI.
    However when you change a setting, for example username
    mapping, you get acknowledgement that the user registry has
    been updated, but when we view the settings later, we can't see
    that change applied. This applies to all the Mapping fields
    of all the OIDC registry type.
    - Reproduction steps
    -----------------------
    1. Create a new OIDC User Registry with for example type
    Windows Live
    2. Modify the User Registry by changing the Mapping field
    username to "name".
    3. Save
    4. View the created User Registry again
    5. The setting shows still as the default "sub".
    The change seems to be persisting in the backend and only
    affecting the UI.
    

Local fix

Problem summary

  • When creating an OIDC registry in the API Connect UI and change
    mapping settings to map the claims differently from the default,
    changes are not reflected in the UI.
    
    The changes are saved but not reflected in the UI.
    

Problem conclusion

  • The product is updated in version 10.0.1 to address the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI81728

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    18X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-22

  • Closed date

    2020-10-27

  • Last modified date

    2020-10-27

  • 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

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X"}]

Document Information

Modified date:
28 October 2020