Error Processing Profile Request

[Cantor, Scott]

> We are hoping to upgrade soon, but in the meantime we have this issue.
> Is there a workaround?

What you're doing is inappropriate, so the workaround is not to do it. There is no value in what you're trying to do, it's wrong. See below.

> <!-- Name Identifier related attributes -->
>     <resolver:AttributeDefinition id="transientId" xsi:type="TransientId"

A transientID is a per-session random value that's just a placeholder. It is *never* useful to pass it with some other Format identifier because it would never "fit" any use case that would demand an alternative Format.

>         <resolver:AttributeEncoder xsi:type="SAML1StringNameIdentifier"
>             xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
> nameFormat="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified" />
>         <resolver:AttributeEncoder xsi:type="SAML2StringNameID"
> xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
>             nameFormat="urn:oasis:names:tc:SAML:1.1:nameid-
> format:unspecified" />

So, this set of encoders above is just wrong. I don't know why it happens to be failing in that way, but it's not a bug that anybody needs to work around, just don't do it. You have no reason to do it, and whatever reason you have is a mistake on your part, a misunderstanding.

-- Scott