Home
Products
Downloads
Purchase
Support
Forums
About
Back
Forums, Documentation & Knowledge Base - ComponentSpace
Register
Login
ComponentSpace
Forums
Home
»
ComponentSpace Support Forums
»
Questions - SAML SSO for ASP.NET
»
CanSLO from ApiController using SignOut API
CanSLO from ApiController using SignOut API
Post Reply
CanSLO from ApiController using SignOut API
View
Options
Author
Message
amitm
amitm
Posted 4 Years Ago
#10940
New Member
Group: Forum Members
Posts: 2,
Visits: 5
Hello Team,
I would like to implement SLO using SignOut API written in one of the controller inherited from ApiController. This
SignOut API is getting called from client written in typescript. I am unable to get the
Response
object in my controller inherited from
ApiController
to pass into InitiateSLO method
E.g. SAMLIdentityProvider.InitiateSLO(Response, null, null);
Am i doing anything wrong, please suggest how can I use the
(SLO)
or
Response object under web api controller?
Reply
ComponentSpace
ComponentSpace
Posted 4 Years Ago
#10943
ComponentSpace Development
Group: Administrators
Posts: 3.2K,
Visits: 11K
SAMLIdentityProvider.InitiateSLO will result in a 302 HTTP response being returned to the browser. The redirect URL is the logout service of the service provider with the SAML logout request encoded as a query string parameter.
Calling this method within a web API is problematic. The client presumably is expecting a 200 HTTP response and won't be able to handle the 302 correctly.
Our recommendation is to not invoke SAML SSO or SLO from a web API. Instead, the client should have the browser initiate an HTTP Get to particular endpoints to initiate SSO or SLO.
Regards
ComponentSpace Development
Reply
amitm
amitm
Posted 4 Years Ago
#10948
New Member
Group: Forum Members
Posts: 2,
Visits: 5
Hello Team,
Thanks for the response, If I say same way (in API within an APIController), if I would like initiate SLO from ServiceProvider will that be recommended ?
E.g. SAMLServiceProvider.InitiateSLO(Response, null, null);
Reply
ComponentSpace
ComponentSpace
Posted 4 Years Ago
#10949
ComponentSpace Development
Group: Administrators
Posts: 3.2K,
Visits: 11K
Calling SAMLIdentityProvider.InitiateSLO or SAMLServiceProvider.InitiateSLO within a web API is problematic for the reasons mentioned above. Both result in a 302 HTTP response.
Regards
ComponentSpace Development
Reply
GO
Post Reply
Similar Topics
Post Quoted Reply
Login
Existing Account
Email Address:
Password:
Reset Your Password
Remember Me
Select a Forum....
ComponentSpace Support Forums
Questions - SAML SSO for ASP.NET
Questions - SAML SSO for ASP.NET Core
Questions - OpenID for ASP.NET Core
ComponentSpace Documentation
Announcements
Documentation - SAML SSO for ASP.NET
Documentation - SAML SSO for ASP.NET Core
Documentation - OpenID for ASP.NET Core
ComponentSpace Knowledge Bases
Knowledge Base - SAML SSO for ASP.NET
Knowledge Base - SAML SSO for ASP.NET Core
Knowledge Base - OpenID for ASP.NET Core
Explore
Home
Latest
Popular
Search
Tags
Forums
ComponentSpace Support Forums
Questions - SAML SSO for ASP.NET
Questions - SAML SSO for ASP.NET Core
Questions - OpenID for ASP.NET Core
ComponentSpace Documentation
Announcements
Documentation - SAML SSO for ASP.NET
Documentation - SAML SSO for ASP.NET Core
Documentation - OpenID for ASP.NET Core
ComponentSpace Knowledge Bases
Knowledge Base - SAML SSO for ASP.NET
Knowledge Base - SAML SSO for ASP.NET Core
Knowledge Base - OpenID for ASP.NET Core
Forums, Documentation & Knowledge Base - ComponentSpace
Login
Register
Search
Flat Ascending
Flat Descending
Threaded
Subscribe to topic
Print This Topic
Goto Topics Forum
Jump To Page
Jump To Page