PK79214: Specifying a URL for a CRL for JAX-RPC WS-Security does not work

Fixes are available

APAR status

Closed as program error.

Error description

The JAX-RPC WS-Security Configuration for a Certificate
Revocation List (CRL) is only working with the specification in
the form of a file.  Any other specification of the CRL, such
as a URL, results in an exception, and the application will not
start.

Local fix

```
Specify the CRL as a file.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V6.1   *
*                  and V7.0 users of WS-Security enabled       *
*                  JAX-RPC applications using Certificate      *
*                  Revocation Lists (CRLs)                     *
****************************************************************
* PROBLEM DESCRIPTION: Specifying a URL for a CRL for          *
*                      JAX-RPC WS-Security does not work       *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this APAR. *
****************************************************************
The JAX-RPC WS-Security Configuration for a Certificate
Revocation List (CRL) is only working with the specification in
the form of a file.

If the CRL is specified as a URL, the WS-Security runtime will
log an exception similar to the following and the application
will not start:

[4/27/09 15:31:48:296 CDT] 0000001d SecurityHooks E
WSWS1042E: An error occurred in loading the configuration for
com.ibm.ws.webservices.wssecurity.handler.WSEMFRequestConsumerCo
nfig. The exception is
com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5310E:
Unable to open an X509 CRL file:
c:\WebSphere\AppServer\profiles\myProfile\http:\ausgsa.ibm.com\m
yx509crl.crl: java.io.FileNotFoundException:
http:\ausgsa.ibm.com\myx509crl.crl (The filename, directory
name, or volume label syntax is incorrect.)
at
com.ibm.wsspi.wssecurity.SoapSecurityException.format
(SoapSecurityException.java:82)
at
com.ibm.xml.soapsec.util.ConfigUtil.getX509CRL
(ConfigUtil.java:809)
at
com.ibm.ws.webservices.wssecurity.handler.WSEMFRequestConsumerCo
nfig.init(WSEMFRequestConsumerConfig.java:1184)
at
com.ibm.ws.webservices.wssecurity.handler.WSEMFRequestConsumerCo
nfig.<init>(WSEMFRequestConsumerConfig.java:181)

Problem conclusion

The WS-Security runtime is updated to allow the CRL to be
specified in the form of both a file and a URL.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 7.0.0.5.  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
PK79214
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-22
Closed date
2009-04-28
Last modified date
2009-04-28

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK84936

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK79214: Specifying a URL for a CRL for JAX-RPC WS-Security does not work

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?