SAML Application XML Error: "failed to find registered serviceprovider"

I have a ZITADEL Application within a Project configured with SAML authentication and I am attempting to start the login process using https://<ZITADEL-DOMAIN>/saml/v2/SSOhttps://<ZITADEL-DOMAIN>/saml/v2/SSO.

I am using the saml2-jssaml2-js (https://www.npmjs.com/package/saml2-js) library to generate the XML requests and this is the XML it sends as the SAMLRequestSAMLRequest query parameter (deflated and base64-encoded in reality). All instances of the ZITADEL domain have been replaced with <ZITADEL-DOMAIN><ZITADEL-DOMAIN> for the sake of sharing.

<?xml version="1.0"?>
<AuthnRequest
    xmlns="urn:oasis:names:tc:SAML:2.0:protocol"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_4d3cdb03fbfe470b1c0c9968587de81b2dc92d93c2" IssueInstant="2024-08-15T17:26:18.024Z" Destination="https://<ZITADEL-DOMAIN>/saml/v2/SSO" AssertionConsumerServiceURL="http://localhost:3000/api/auth/signin/sana-saml" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST">
    <saml:Issuer>https://<ZITADEL-DOMAIN>/saml/v2/metadata</saml:Issuer>
    <NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" AllowCreate="true"/>
</AuthnRequest>

<?xml version="1.0"?>
<AuthnRequest
    xmlns="urn:oasis:names:tc:SAML:2.0:protocol"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_4d3cdb03fbfe470b1c0c9968587de81b2dc92d93c2" IssueInstant="2024-08-15T17:26:18.024Z" Destination="https://<ZITADEL-DOMAIN>/saml/v2/SSO" AssertionConsumerServiceURL="http://localhost:3000/api/auth/signin/sana-saml" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST">
    <saml:Issuer>https://<ZITADEL-DOMAIN>/saml/v2/metadata</saml:Issuer>
    <NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" AllowCreate="true"/>
</AuthnRequest>

npm

saml2-js

SAML 2.0 node helpers. Latest version: 4.0.2, last published: a year ago. Start using saml2-js in your project by running npm i saml2-jsnpm i saml2-js. There are 30 other projects in the npm registry using saml2-js.

SAML Application XML Error: "failed to find registered serviceprovider"

<?xml version="1.0"?>
<AuthnRequest
    xmlns="urn:oasis:names:tc:SAML:2.0:protocol"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_4d3cdb03fbfe470b1c0c9968587de81b2dc92d93c2" IssueInstant="2024-08-15T17:26:18.024Z" Destination="https://<ZITADEL-DOMAIN>/saml/v2/SSO" AssertionConsumerServiceURL="http://localhost:3000/api/auth/signin/sana-saml" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST">
    <saml:Issuer>https://<ZITADEL-DOMAIN>/saml/v2/metadata</saml:Issuer>
    <NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" AllowCreate="true"/>
</AuthnRequest>

<?xml version="1.0"?>
<AuthnRequest
    xmlns="urn:oasis:names:tc:SAML:2.0:protocol"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_4d3cdb03fbfe470b1c0c9968587de81b2dc92d93c2" IssueInstant="2024-08-15T17:26:18.024Z" Destination="https://<ZITADEL-DOMAIN>/saml/v2/SSO" AssertionConsumerServiceURL="http://localhost:3000/api/auth/signin/sana-saml" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST">
    <saml:Issuer>https://<ZITADEL-DOMAIN>/saml/v2/metadata</saml:Issuer>
    <NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" AllowCreate="true"/>
</AuthnRequest>

npm

saml2-js

SAML Application XML Error: "failed to find registered serviceprovider"

SAML Application XML Error: "failed to find registered serviceprovider"

Continue the conversation

ZITADEL

Continue the conversation

ZITADEL

Similar Threads