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
Your saml.config includes the configuration but it also needs a 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 as well as the . For example:
<ServiceProvider
Name=“<a href=“https://ExampleServiceProvider””>https://ExampleServiceProvider"
Description=“Example Service Provider”
AssertionConsumerServiceUrl=“~/SAML/AssertionConsumerService.aspx”>
The configuration must match with the relying party configuration in ADFS. If you supplied the IdP with your SAML metadata, the 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
[quote][/quote]
Your saml.config includes the configuration but it also needs a 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 as well as the . For example:
<ServiceProvider
Name="https://ExampleServiceProvider"
Description="Example Service Provider"
AssertionConsumerServiceUrl="~/SAML/AssertionConsumerService.aspx">
The configuration must match with the relying party configuration in ADFS. If you supplied the IdP with your SAML metadata, the 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
If you take a look at the ExampleServiceProvider's saml.config, you'll see it includes a as well as the . For example:
<ServiceProvider
Name="https://ExampleServiceProvider"
Description="Example Service Provider"
AssertionConsumerServiceUrl="~/SAML/AssertionConsumerService.aspx">
The configuration must match with the relying party configuration in ADFS. If you supplied the IdP with your SAML metadata, the 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 into SAML.config file but
getting the same exception
Relying Party Trust Proerties
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'" ?
You added a rather than a to your saml.config.
As your application is acting as the service provider you need a entry which includes configuration information about your local service provider. You also need a entry for each partner identity provider website.
The entry is applicable if your site were the identity provider rather than the service provider. Your would then have an and 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.
[quote][/quote]
You added a rather than a to your saml.config.
As your application is acting as the service provider you need a entry which includes configuration information about your local service provider. You also need a entry for each partner identity provider website.
The entry is applicable if your site were the identity provider rather than the service provider. Your would then have an and 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.
As your application is acting as the service provider you need a entry which includes configuration information about your local service provider. You also need a entry for each partner identity provider website.
The entry is applicable if your site were the identity provider rather than the service provider. Your would then have an and 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 tag rather than in my SAML.Config file. The exception had gone as I changed tag from to and configure tag correspond to Relying Party Trust configuration
Thanks for the update.