ComponentSpace

Forums



A local identity or service provider must be configured


A local identity or service provider must be configured

Author
Message
LacLacey
LacLacey
New Member
New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)

Group: Forum Members
Posts: 5, Visits: 48
I'm getting an exception A local identity or service provider must be configured, when calling SAML2.0 API InitiateSSO(HttpResponseBase httpResponse, string relayState, string partnerIdP ), although I have registerd my machine(PC) into Server 2012R2 Datacenter and also created Relying Party Trust in ADFS.

SAML.Config

Web.Config


MVC Action Index


ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)

Group: Administrators
Posts: 2.9K, Visits: 9.4K
Your saml.config includes the <PartnerIdentityProviders> configuration but it also needs a <ServiceProvider> element which contains the configuration information specific to your application acting as the service provider.

If you take a look at the ExampleServiceProvider's saml.config, you'll see it includes a <ServiceProvider> as well as the <PartnerIdentityProviders>. For example:


<ServiceProvider
Name="https://ExampleServiceProvider"
Description="Example Service Provider"
AssertionConsumerServiceUrl="~/SAML/AssertionConsumerService.aspx">
<LocalCertificates>
  <Certificate FileName="Certificates\sp.pfx" Password="password"/>
</LocalCertificates>
</ServiceProvider>



The <ServiceProvider> configuration must match with the relying party configuration in ADFS. If you supplied the IdP with your SAML metadata, the <ServiceProvider> Name matches the entityID in your metadata. This corresponds to the relying party identifier in ADFS.

For more information, please refer to our ADFS Relying Party Integration Guide.

https://www.componentspace.com/Forums/9358/ADFS-Integration-Guides


Regards
ComponentSpace Development
LacLacey
LacLacey
New Member
New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)

Group: Forum Members
Posts: 5, Visits: 48
ComponentSpace - 6/24/2020
Your saml.config includes the <PartnerIdentityProviders> configuration but it also needs a <ServiceProvider> element which contains the configuration information specific to your application acting as the service provider.

If you take a look at the ExampleServiceProvider's saml.config, you'll see it includes a <ServiceProvider> as well as the <PartnerIdentityProviders>. For example:


<ServiceProvider
Name="https://ExampleServiceProvider"
Description="Example Service Provider"
AssertionConsumerServiceUrl="~/SAML/AssertionConsumerService.aspx">
<LocalCertificates>
  <Certificate FileName="Certificates\sp.pfx" Password="password"/>
</LocalCertificates>
</ServiceProvider>



The <ServiceProvider> configuration must match with the relying party configuration in ADFS. If you supplied the IdP with your SAML metadata, the <ServiceProvider> Name matches the entityID in your metadata. This corresponds to the relying party identifier in ADFS.

For more information, please refer to our ADFS Relying Party Integration Guide.

https://www.componentspace.com/Forums/9358/ADFS-Integration-Guides

Thanks for your response. I included the <ServiceProvider> into SAML.config file but
getting the same exception


Relying Party Trust Proerties

https://www.componentspace.com/Forums/Uploads/Images/163cbba8-3009-484d-8e6b-673e.png

https://www.componentspace.com/Forums/Uploads/Images/f1cbfba6-6dc6-4815-9bf3-ff1b.png

https://www.componentspace.com/Forums/Uploads/Images/c6fa75ae-157a-4413-93d3-c5c8.png

https://www.componentspace.com/Forums/Uploads/Images/1d758c68-13c7-4136-9ae6-473e.png

https://www.componentspace.com/Forums/Uploads/Images/a231c096-8eaa-40ba-8a21-c438.png

https://www.componentspace.com/Forums/Uploads/Images/039b5a08-5fe6-446d-865c-0e85.png

EntityID of Federation Metadata


so what's wrong or missing in my configuration ?
why I'm getting the exception "A local identity or service provider must be configured'" ?

ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)

Group: Administrators
Posts: 2.9K, Visits: 9.4K
You added a <PartnerServiceProvider> rather than a <ServiceProvider> to your saml.config.

As your application is acting as the service provider you need a <ServiceProvider> entry which includes configuration information about your local service provider. You also need a <PartnerIdentityProvider> entry for each partner identity provider website.

The <PartnerServiceProvider> entry is applicable if your site were the identity provider rather than the service provider. Your would then have an <IdentityProvider> and <PartnerServiceProvider> entries.

Please take a look at the ExampleServiceProvider's saml.config for an example configuration.

Also, take a look at the ADFS Relying Party Integration Guide previously mentioned. The screenshots of the relying party properties show that you are using identifiers and URLs of ADFS rather than the ExampleServiceProvider.

Regards
ComponentSpace Development
LacLacey
LacLacey
New Member
New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)New Member (12 reputation)

Group: Forum Members
Posts: 5, Visits: 48
ComponentSpace - 6/29/2020
You added a <PartnerServiceProvider> rather than a <ServiceProvider> to your saml.config.

As your application is acting as the service provider you need a <ServiceProvider> entry which includes configuration information about your local service provider. You also need a <PartnerIdentityProvider> entry for each partner identity provider website.

The <PartnerServiceProvider> entry is applicable if your site were the identity provider rather than the service provider. Your would then have an <IdentityProvider> and <PartnerServiceProvider> entries.

Please take a look at the ExampleServiceProvider's saml.config for an example configuration.

Also, take a look at the ADFS Relying Party Integration Guide previously mentioned. The screenshots of the relying party properties show that you are using identifiers and URLs of ADFS rather than the ExampleServiceProvider.

Thank you so much for your time. My application is acting as Service Provider so I was creating the <PartnerServiceProvider> tag rather than <ServiceProvider> in my SAML.Config file. The exception had gone as I changed tag from <PartnerServiceProvider> to <ServiceProvider> and configure <ServiceProvider> tag correspond to Relying Party Trust configuration

ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)ComponentSpace Development (4K reputation)

Group: Administrators
Posts: 2.9K, Visits: 9.4K
Thanks for the update.

Regards
ComponentSpace Development
GO


Similar Topics


Execution: 0.000. 3 queries. Compression Enabled.
Login
Existing Account
Email Address:


Password:


Social Logins

Select a Forum....









Forums, Documentation & Knowledge Base - ComponentSpace


Search