Idp v3 (upgraded) and Google app

[Cantor, Scott]

On 6/18/15, 1:48 PM, "users on behalf of C G" <users-bounces at shibboleth.net on behalf of ci_98yr at yahoo.com> wrote:

>Have this upgraded (from v2 to 3.1.1) and trying to get this working with google apps
>Works with V2, but for v3 idp resp Google throws unknown acc :)

Well, you're not triggering any alternative NameID format, so it's using the default/transient. An upgraded V2 configuration should mostly be doing what it was doing before in terms of NameID generation, so that suggests you made additional changes or alterations involving newer features or config formats, such as updating to a V3 relying-party.xml, which would remove critical settings that were being used in the old file to trigger behavior unless you translated all those settings across.

>Tried the one below rule on adding to relying-party.xml and nameid..xml
>http://shibboleth.1660669.n2.nabble.com/Google-Apps-with-IdPv3-tt7612963.html#a7612972

That would apply to a non-upgraded system or to making changes to do it the "new" way rather than relying on the older config format and the attribute-resolver to generate the NameIDs.

But yes, that is the "updated" way to do it. That would also typically include removing the deprecated NameID encoder from the attribute definition.

>But getting util:list not bound error

That's not a self-explanatory error message.

>And I believe 
>xmlns:util="http://www.springframework.org/schema/util"Is already in mvc xml

That's a namespace declaration in a single XML file that certainly has nothing to do with these use cases. XML files are self-contained, they have nothing to do with each other in most respects.

-- Scott