Hi.
I installed your SAML package and I can see your example.
There are some sample how to generate metadata and read metadata.
But one thing I don’t understand, what if some vendor provides saml metadata, and how can I connect to their server with their metadata?
You guys doesn’t have any sample why the metadata is generated.
Would you mind to let me know how can I consume saml metadata from other vendor by using your library?
Thanks
This is described in our SAML Metadata Guide.
https://www.componentspace.com/Forums/9354/SAML-Metadata-Guide
You can use CreateMetadata to generate your metadata to distribute to partner providers.
You can use ImportMetadata to import a partner provider’s metadata to update your SAML configuration file (saml.config).
[quote][/quote]
This is described in our SAML Metadata Guide.
https://www.componentspace.com/Forums/9354/SAML-Metadata-Guide
You can use CreateMetadata to generate your metadata to distribute to partner providers.
You can use ImportMetadata to import a partner provider's metadata to update your SAML configuration file (saml.config).
https://www.componentspace.com/Forums/9354/SAML-Metadata-Guide
You can use CreateMetadata to generate your metadata to distribute to partner providers.
You can use ImportMetadata to import a partner provider's metadata to update your SAML configuration file (saml.config).
Hi!
Thanks for your answer.
I understand there are already sample importing & exporting metadata.
But my point is after importing, how can I connect to their login page?
Sorry maybe I am confused. I saw how to communicate between SP and IdP
but that happens at vendor's server side.(in my case)
At my side, I am just client and I don't have SP nor IdP.
I just wanted to consume their service.
Metadata guides contains in regard of this?
Thanks.
The SP and IdP are web applications/sites.
A user with a browser navigates to one of these sites and initiates SSO.
When you say you’re just the client, rather than the SP or IdP, could you please elaborate?
Do you want to know what URL to use in the browser?
If so, you need to ask the vendor.
The URLs in the metadata are for SAML communications rather than for a user to browse to to initiate SSO.
[quote][/quote]
The SP and IdP are web applications/sites.
A user with a browser navigates to one of these sites and initiates SSO.
When you say you're just the client, rather than the SP or IdP, could you please elaborate?
Do you want to know what URL to use in the browser?
If so, you need to ask the vendor.
The URLs in the metadata are for SAML communications rather than for a user to browse to to initiate SSO.
A user with a browser navigates to one of these sites and initiates SSO.
When you say you're just the client, rather than the SP or IdP, could you please elaborate?
Do you want to know what URL to use in the browser?
If so, you need to ask the vendor.
The URLs in the metadata are for SAML communications rather than for a user to browse to to initiate SSO.
HM..
Right. Sorry again, I was confused from beginning.
So what you are saying is if vendor provides metadata to me, then I need to be one of roles, SP or IdP.
If I am purely a web user, then I don't need metadata at all.
Am I correct?
By the way, thanks for your quick answer!!
Also your example is really helpful.
cheers,
That’s correct.
Metadata is a standard way to exchange SAML configuration information between IdPs and SPs.
For example, if you were the SP then you would use the IdP’s metadata to configure your system to support SSO with that IdP.
If you’d a web user, you don’t need the metadata. You would simply browse to whichever web site.
Feel free to ask any other questions you might have.
You’re welcome.