PI96187: Update bluemixUtility command for data sovereignty regulations

Fixes are available

APAR status

Closed as program error.

Error description

The on-premise bluemixUtility command in WebSphere
Application Server Liberty and traditional supports
configuring on-premise servers to use certain IBM Cloud
services. The command accomplishes this by logging into an
enterprise customer's IBM Cloud account, obtaining the
credentials for the customer's IBM Cloud service, and then
using an IBM Cloud application to generate the appropriate
configuration files for the on-premise server.

Presently, after obtaining the credentials for the IBM Cloud
service, the credentials may be sent to an IBM Cloud
application running in a different data center than the data
center that was logged into when running the bluemixUtility
command.

In order to prevent credentials from being sent to a
different
data center, the bluemixUtility command should be updated to
not pass the IBM Cloud service credentials to a data center
other
than the one that was logged into and from where the
credentials were obtained. The transfer of credentials to
another
data center may be subject to regulation. If credentials are
not
transferred to another data center, then there is no need to
determine whether a credential transfer is subject to a data
transfer regulation.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server bluemixUtility command               *
****************************************************************
* PROBLEM DESCRIPTION: bluemixUtility command may failover to  *
*                      data center outside region              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After the bluemixUtility command obtains the credentials for an
IBM Cloud service, if the IBM Cloud application that creates the
configuration files using those credentials is not available in
the same data center, the bluemixUtility command will failover
to the same IBM Cloud application in another data center,
passing the IBM Cloud service credentials outside the original
data center. The returned configuration files will be correct,
but the IBM Cloud service credentials may have been passed
outside the original data center without notification.

Problem conclusion

The bluemixUtility command in WebSphere Application Server
Liberty and traditional will be updated to only connect to the
data center that has been explicitly logged into. The IBM Cloud
application to create configuration data will be made available
in all data centers for the supported IBM Cloud services.

The fix for this APAR is currently targeted for inclusion in fix
pack 9.0.0.8 for WebSphere Application Server and 18.0.0.2 for
WebSphere Application Server Liberty.  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
PI96187
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-04
Closed date
2018-05-01
Last modified date
2018-05-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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

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

Document Information

Modified date:
04 May 2022

Tips

PI96187: Update bluemixUtility command for data sovereignty regulations

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?