Hi,
Is it possible to use ComponentSpace SAML 2.0 in windows application (desktop app) ?
If yes, could please guide me in the same? Any link or code sample?
Thanks,
Lokesh
Hi Lokesh
The most commonly supported SAML profile (use case) is web browser SSO.
This involves two web applications or sites, the identity provider (IdP) and the service provider (SP), and a user agent which typically is a browser.
The most commonly supported SAML bindings (transports) are HTTP-Post and HTTP-Redirect.
Using theses transports, messages are not sent directly between the IdP and SP but instead are sent via the browser.
Our SAML API supports enabling SAML SSO in an ASP.NET web application.
It can’t be called from a Windows or other non-web application.
You could embed a browser control in your Windows application to support SAML SSO.
Some of our customers have done this but we don’t have any example projects demonstrating this.
Remember that there will still be IdP and SP web applications.
Your Windows application is effectively the browser in any SAML SSO flow.
[quote][/quote]
Hi Lokesh
The most commonly supported SAML profile (use case) is web browser SSO.
This involves two web applications or sites, the identity provider (IdP) and the service provider (SP), and a user agent which typically is a browser.
The most commonly supported SAML bindings (transports) are HTTP-Post and HTTP-Redirect.
Using theses transports, messages are not sent directly between the IdP and SP but instead are sent via the browser.
Our SAML API supports enabling SAML SSO in an ASP.NET web application.
It can't be called from a Windows or other non-web application.
You could embed a browser control in your Windows application to support SAML SSO.
Some of our customers have done this but we don't have any example projects demonstrating this.
Remember that there will still be IdP and SP web applications.
Your Windows application is effectively the browser in any SAML SSO flow.
The most commonly supported SAML profile (use case) is web browser SSO.
This involves two web applications or sites, the identity provider (IdP) and the service provider (SP), and a user agent which typically is a browser.
The most commonly supported SAML bindings (transports) are HTTP-Post and HTTP-Redirect.
Using theses transports, messages are not sent directly between the IdP and SP but instead are sent via the browser.
Our SAML API supports enabling SAML SSO in an ASP.NET web application.
It can't be called from a Windows or other non-web application.
You could embed a browser control in your Windows application to support SAML SSO.
Some of our customers have done this but we don't have any example projects demonstrating this.
Remember that there will still be IdP and SP web applications.
Your Windows application is effectively the browser in any SAML SSO flow.
Yes,
Going with the same approach.
Thanks for your reply.
You’re welcome.