PM70833: SOME WS-SECURITY APIS REQUIRE THAT BASE64 DATA BE DECODED, BUT DOES NOT PROVIDE A METHOD TO DECODE THE DATA

Fixes are available

APAR status

Closed as program error.

Error description

The LTPA token in the HTTP header is Base64 encoded.  If you
want to pass an LTPA token into the LTPA token generator, you
must pass token bytes that are not encoded.  So, if you want
to pick the LTPA token off of the HTTP header and pass it to
the LTPA token generator, you must first decode the token
before sending it to the LTPA token generator.  The
WS-Security runtime does not provide a method to decode the
token bytes.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  developers of WS-Security enabled JAX-WS    *
*                  applications                                *
****************************************************************
* PROBLEM DESCRIPTION: Some WS-Security APIs require that      *
*                      Base64 data be decoded, but a method    *
*                      to decode the data is not provided      *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this       *
*                  APAR.                                       *
****************************************************************
The LTPA token in the HTTP header is Base64 encoded.  If you
want to pass an LTPA token into the LTPA token generator, you
must pass token bytes that are not encoded.  So, if you want
to pick the LTPA token off of the HTTP header and pass it to
the LTPA token generator, you must first decode the token
before sending it to the LTPA token generator.  The
WS-Security runtime does not provide a method to decode the
token bytes.
There are other actions that an application developer is
expected to perform to interact with the WS-Security engine
that may be either difficult or unclear how to implement.

Problem conclusion

Two new utility classes are created in WS-Security for use by
application developers:

com.ibm.websphere.wssecurity.wssapi.WSSUtilFactory
com.ibm.wsspi.wssecurity.wssapi.OMStructureFactory


WSSUtilFactory contains some general utility methods that an
application developer may find helpful when interacting with
WS-Security through WSSAPIs or JAAS login modules.

OMStructureFactory is provided so that an application
developer can use the WS-Security engine's implementation
class for OMStructure instead of having to create their own
when implementing custom tokens.


WSSUtilFactory contains the following methods:

WSSUtilFactory getInstance() throws WSSException;
String encode(byte[] data);
byte[] decode(String data);
KeyStore getKeyStore(String keyStoreRef) throws WSSException;
KeyStore getKeyStore(String storeType, String storePath,
char[] storePass) throws WSSException;
Map getHTTPRequestHeaders(MessageContext msgContext);
Map getHTTPRequestHeaders(Map wssContext);
Map getHTTPRequestHeaders(CallbackHandler handler) throws
WSSException;
Map getWSSContext(CallbackHandler handler) throws WSSException;
MessageContext getMessageContext(Map wssContext);
MessageContext getMessageContext(CallbackHandler handler)
throws WSSException;
Map getCallbackHandlerProperties(Map wssContext);
Map getCallbackHandlerProperties(CallbackHandler handler)
throws WSSException;
OMElement getProcessingElement(Map wssContext);
org.w3c.dom.Element getDOMProcessingElement(Map wssContext);
void setConsumedToken(Map WSSContext, SecurityToken token);
void setConsumedToken(Map WSSContext, List tokens);
void setGeneratedToken(Map WSSContext, SecurityToken token);
void setGeneratedToken(Map WSSContext, List tokens);

OMStructureFactory contains the following methods:

OMStructureFactory getInstance() throws WSSException;
com.ibm.wsspi.wssecurity.wssapi.OMStructure
  getOMStructure(OMElement node);
com.ibm.wsspi.wssecurity.wssapi.OMStructure
  getOMStructure(org.w3c.dom.Element element) throws Exception;


To use methods in each class, first obtain an instance of the
class with the getInstance() method, then invoke the methods
through that insance.  For instance:

WSSUtilFactory utilFactory = WSSUtilFactory.getInstance();
byte [] decodedBytes = factory.decode(encodedBytes);

OMStructureFactory omsFactory =
  OMStructureFactory.getInstance();
OMStructure om = omsFactory.getOMStructure(myOmElement);


Full javadoc for these new classes and methods will be availble
in the information center.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.27, 8.0.0.6, 8.5.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
PM70833
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-14
Closed date
2012-10-15
Last modified date
2012-10-15

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

R700 PSY
UP
R800 PSY
UP
R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM70833: SOME WS-SECURITY APIS REQUIRE THAT BASE64 DATA BE DECODED, BUT DOES NOT PROVIDE A METHOD TO DECODE THE DATA

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?