IBM Support

LI83175: PORTAL OIDC FLOW BREAKS WHILE USING IN-CLUSTER COMMUNICATION

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 using a Portal service, which has been registered to the
    management using in-cluster communication, the OIDC redirect is
    broken for the portal users when trying to login using an OIDC
    user registry.
    

Local fix

  • not use in-cluster communication
    

Problem summary

  • Portal site users can't use the OIDC registry to login when the
    portal service has been registered using in-cluster
    communication.
    

Problem conclusion

  • Fix targeted for 10.0.5.8 and 10.0.8.0 releases
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI83175

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-05-15

  • Closed date

    2024-06-21

  • Last modified date

    2024-06-21

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
21 June 2024