v3.2 - unsupportable identifier -Name ID

[Ramaiah, Vanna G.]

Solved it by turning of the legacy in sevices.xml. Now I have to migrate all the relying party's one by one. Thanks again.

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Ramaiah, Vanna G.
Sent: Wednesday, February 22, 2017 6:47 PM
To: 'Shib Users' <users at shibboleth.net>
Subject: RE: v3.2 - unsupportable identifier -Name ID



I very much got that point now. So, I put back the original relying-party.xml from V3.2 installation. There was no relying party's defined in it. I am getting this error.
Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'shibboleth.UnverifiedRelyingParty' defined in file [/opt/shibboleth-idp/conf/relying-party.xml]: Could not resolve parent bean definition 'RelyingParty'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'RelyingParty' is defined

The reason I did fresh installation was our server didn't support all the minimum requirements of V3. The system admin team suggested to  do fresh installation. Thanks for all your help.

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, February 22, 2017 6:19 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: v3.2 - unsupportable identifier -Name ID



On 2/22/17, 6:00 PM, "users on behalf of Ramaiah, Vanna G." <users-bounces at shibboleth.net on behalf of ramaiah at musc.edu> wrote:

> I found what's incorrect. As I imported the relying-party.xml from V2 
> on fresh installation of V3.2, the header of the file has the following but beans were not imported.

If you want to upgrade, then you upgrade. That means you install over top of V2. At that point your old relying-party.xml file will be used and it will work.

You cannot start from scratch and then use the old file, it doesn't work that way. You are required to learn the *new* syntax and copy the *meaning* of your old settings over. You cannot just copy the XML. The files have different schemas defining their content, even if they're structurally similar to make things easier to transfer over.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net





--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net