Hi, Thomas.
First, you shouldn't use 2.4.3, 2.4.4 is the most recent package.
Regarding that part:
>The reason it wasn't showing up in /opt/idp/relying-party.xml is I did not have "Configure Specific Relying Party" checked in the trust relationship.
That's not quite true. You are right that a separate `RelyingParty` element will only appear if "Configure Specific Relying Party" feature is used, but even when it's not being used, everything should work as default relying party's definition will be used (that's by design). Without using this feature, the only sign telling you your configuration was applied in this file will be appearing of a new `medataProvider` element. You also should have checked what status it had in the list of existing SAML TR's in web UI, like "Active", "Inactive", "Validation is scheduled" etc. It's hard to say what was the cause now.
Also please take into account that changes to SAML TRs are not applied right away, may take several minutes. We also had one bug in an earlier build resulting sometimes in situation when those files won't be updated after TR is created until this TR will be changed in any way once more, or until Tomcat is restarted.
Should we close the ticket now?