Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Fixed In:
14.0.0
Opened: Jul 07, 2017 Severity: 3-Major
When problems occur during the import or export of SAML metadata for SP or IdP, a message is logged, but the information is insufficient to help determine why the import/export failed. The system logs and error message similar to the following: MCP Error01070712:3: apm aaa saml-sp-connector <sp-connector> unable to parse metadata file /var/tmp/1498598319464.upload.
Generic message is logged. The message contains insufficient information for troubleshooting.
Metadata import/export failure for SAML SP and IdP.
There is no workaround.
This release enhances the error message logged during import/export failure of SAML SP or IdP metadata to provide additional info to help with troubleshooting. Examples: MCP Error01070712:3: apm aaa saml-sp-connector sp1 unable to parse metadata file /var/tmp/1506737815551.upload: invalid document structure . MCP Error01070712:3: apm aaa saml-sp-connector sp2 unable to parse metadata file /var/tmp/1506737894866.upload: unable to create converter for 'ABC' encoding. In addition, the SAX(XML parser) exception that is thrown is now modified to log the line number and column number of the location in the metadata file where exception occurred. Example: /var/tmp/mcpd.out - SAX Exception: line 1, char 40 message: invalid document structure.