Version Affected: All
When using the Transformation Engine on a WSFed realm, depending on the XSLT being used, the AttributeStatement in the resulting WSFed SAML assertion will be missing attributes or even completely empty, despite setting the NameSpace field, e.g.:
However switching the realm to issue a SAML assertion instead of WSFed results in the expected output from the transformation engine:
One such scenario that reproduces the problem is if the XSLT has "when" elements without an "otherwise" element, as in this example:
Product defect EE-1781 - The transformation engine is erroneously called twice.
Addressed in the following hotfix packages:
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.