<div dir="ltr"><div dir="ltr"><div>We have switched from IDP v2 to IDP v3 -- still learning the ropes.</div><div><br></div><div>For a cloud service, via saml-tracer, the attributes are encrypted in v3 (whereas in v2, it was unencrypted). The cloud metadata was imported as is (no changes) -- only change is the entry below in relying-party.xml, where I've been trying to send with attribute values unencrypted. Have I missed anything else? Another cloud service is working fine with unencrypted attributes sent, my assumption is that, something I have to do on the vendor's metadata or in the relying-party.xml.<br></div><div><br></div><div><bean parent="RelyingPartyByName"<br>                    c:relyingPartyIds="#{{'<a href="https://cloud">https://cloud</a>'}}"><br>            <property name="profileConfigurations"><br>                <list><br>                    <bean   parent="SAML2.SSO" <br>                            p:authenticationFlows="MFA"<br>                            p:postAuthenticationFlows="#{{'expiring-password'}}"<br>                               p:encryptAssertions="false"<br>                            p:includeAttributeStatement="true"<br>                            p:signAssertions="false"<br>                            p:encryptNameIDs="false"<br>                            p:nameIDFormatPrecedence="#{{'urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified'}}" /><br>                    <ref bean="SAML2.Logout" /><br>                </list><br>            </property><br>      </bean><br></div></div></div>