Projects with SAML [Bug]: about zitadel HOT 5 CLOSED

The console doesn't send the URL to the backend.
It's reproducible with https://mocksaml.com/api/saml/metadata on save and update.
I'll fix it.

from zitadel.

CC @stebenz

Relates to https://discord.com/channels/927474939156643850/1019895518383583323/threads/1206913003312775188

from zitadel.

@HungryHowies Just to differentiate, the expected behaviour still exists but the error you are getting is in reading the Bookstack metadata.xml.
Could you please provide an example metadata.xml from your bookstack instance? So that we can try to sort out what the problem with this file format is? Did you also try to upload the file directly not only through the URL?

from zitadel.

Hey @stebenz

Thx for the reply

@HungryHowies Just to differentiate, the expected behaviour still exists but the error you are getting is in reading the Bookstack metadata.xml.

This is my XML.
NOTE: domain.com is my place holder.

<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" validUntil="2024-02-21T22:03:53Z" 
                             cacheDuration="PT604800S" entityID="https://bookstack.domain.com/saml2/metadata">
<md:SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="false" 
                             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" 
                             Location="https://bookstack.domain.com/saml2/sls"/>
<md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</md:NameIDFormat>
                   <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" 
                               Location="https://bookstack.domain.com/saml2/acs" index="1"/>
            </md:SPSSODescriptor>
</md:EntityDescriptor>

Did you also try to upload the file directly not only through the URL?

Yes that works great using the XML file upload and using Option 3: "Create a minimal metadata file on the fly providing ENTITYID and ACS URL".

Also note that Zitadel Version 2.37.3 works great using the URL.

EDIT: Only reason I bring this up is some customers dont have an option of uploading XMl files.

from zitadel.

@stebenz i guess that the parsing might fail because of a missing header / content type mismatch when retrieving the metadata endpoint.

from zitadel.