Hi everyone, really new to the group here and basically to SF as well so I'm hoping I am constructing this question properly. We are trying to setup SF as the OpenID Connect Provider (OP) for a custom .aspnet.core application (SP/service provider). In reality this asp core app will act as a bridge for an older legacy .net application and the only reason we are having to do this is it appears SF does not support OIDC Hybrid Flow while the libraries Microsoft created for older .net frameworks require to use this flow. Using aspnet.core addresses this problem as we can use Authorization Code flow this way. I see a lot of people here using SAML protocol instead and I am beginning to wonder if we should have taken that direction as well? If anyone has successfully implemented SF as an OP I hope we can connect!
Anyway my question for now really is around session management. When I log out of my asp core app, microsoft's security library does an internal redirect to the "end_session_endpoint" on the OP side to basically log out the user from both the OP side and the SP side. However through the .well-known/openID-configuration discovery endpoint, it does not seem like SF supports an end_session_endpoint so I'm at a loss in trying to figure out how I can log out the user from SF as well?
We love OpenID Connect!
Salesforce supports front-channel-based single logout for OIDC:
https://developer.salesforce.com/docs/atlas.en-us.sso.meta/sso/security_auth_slo_oidc_idp_configuring.htm