thomaskrut

I'm experiencing an issue as described in this closed issue: https://github.com/casdoor/casdoor/issues/3582

I'm running a custom SAML IDP locally and using Casdoor as SP. In the issue, there is a reference to a working configuration in a demo application, but when logging into door.casdoor.com, the SAML provider config is empty and the custom SAML signin method doesn't work ("malformed certificate")

I am able to get around the 403 error, which happens in the cors_filter.go middleware, by either:

1. Adding my SAML IDP URL to the redirect URIs of my Casdoor application
2. Altering the cors filter to always set allowed origins for requests to api/acs/, like it does for the userinfo endpoint for example

Which would be the correct approach?

Yes, I will do that

When using a custom SAML provider in my application, I'm getting this error message after successfully logging into the external IDP.

No user is provisioned. Unlike, for example, using Google Oauth, where non-existing users are automatically created in my Casdoor organization on login.

This seems to imply that no user is created: https://github.com/casdoor/casdoor/blob/master/controllers/auth.go#L931-L934

Thanks, but that is the IDP metadata, I'm looking for the one that has the <SPSSODescriptor> tag

I'm trying to use Casdoor as a SAML service provider with an external IDP. I have added the metadata of the external IDP under my provider settings in Casdoor. However I also need to need to register my SP metadata with the external IDP. Does Casdoor generate SP metadata?