SAML SP Metadata Builder screenshot

SAML SP Metadata Builder

Build SAML service-provider metadata: entity ID, assertion consumer URL, NameID format and the signing flags, with both URLs validated.

Privacy First
0 Runs
Updated 2026-11-17
Runs in your browser
No sign-up, no upload

What the SAML SP Metadata Builder does

The metadata is the SAML 2.0 metadata namespace with one SPSSODescriptor. The assertion consumer service uses the HTTP-POST binding, which is what the decoder page reads, and carries index 0.

The signing flags are one control: AuthnRequestsSigned and WantAssertionsSigned are set together, because a service provider that signs its requests almost always wants signed assertions, and splitting them invites a mismatch.

This builder emits no certificate. A production metadata file usually needs a signing certificate and a second KeyDescriptor; add it from your keystore. The page also does not publish an encryption certificate, so encrypted assertions need hand work.

How to use it

Set the Entity ID, Assertion consumer URL, NameID format and the signing flag, or press Run with the defaults.

Read the SP metadata below: one EntityDescriptor with one SPSSODescriptor.

Check the SP metadata entityID attribute against what you registered with the identity provider — it must match character for character.

Worked example

Input:


Output:

<?xml version="1.0" encoding="UTF-8"?>
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="https://sp.example.com">
  <md:SPSSODescriptor AuthnRequestsSigned="true" WantAssertionsSigned="true">
    <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://sp.example.com/acs" index="0"/>
  </md:SPSSODescriptor>
</md:EntityDescriptor>

Why it runs in your browser

The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.

An `EntityDescriptor` an identity provider can import: your entity ID, your assertion consumer service, the NameID format you expect, and the two signing flags set deliberately.

Both URLs are validated as absolute http(s) URLs, and the entity ID is emitted **exactly as you typed it**, because an entity ID is an identifier that happens to look like a URL.

What it does, and what it does not

The metadata is the SAML 2.0 metadata namespace with one `SPSSODescriptor`. The assertion consumer service uses the HTTP-POST binding, which is what the decoder page reads, and carries index 0.

The signing flags are one control: `AuthnRequestsSigned` and `WantAssertionsSigned` are set together, because a service provider that signs its requests almost always wants signed assertions, and splitting them invites a mismatch.

This builder emits no certificate. A production metadata file usually needs a signing certificate and a second `KeyDescriptor`; add it from your keystore. The page also does not publish an encryption certificate, so encrypted assertions need hand work.

How to use SAML SP Metadata Builder

Set the Entity ID, Assertion consumer URL, NameID format and the signing flag, or press Run with the defaults.

Read the SP metadata below: one EntityDescriptor with one SPSSODescriptor.

Check the SP metadata entityID attribute against what you registered with the identity provider — it must match character for character.

What to Expect

Best for

  • Producing metadata to hand to an IdP administrator
  • Checking the ACS URL and NameID format you configured

Not ideal for

  • A metadata file with certificates, which needs your keystore
  • An IdP's own metadata, which is a different descriptor

What this tool keeps

  • The entity ID exactly as typed
  • The signing flags as one consistent pair

What may need cleanup

  • Add a KeyDescriptor from your certificate
  • Add an encryption certificate if assertions are encrypted

Common errors

  • The page refuses it: entity ID must be an absolute URL

Example use cases

  • Registering a new service provider
  • Reviewing metadata before sending it to an IdP

Sample input

Service provider settings:

Sample output

SP metadata: <?xml version="1.0" encoding="UTF-8"?> …

Who this is for

  • Identity engineers configuring a service provider
  • Anyone asked for 'your SP metadata'

Frequently asked questions

Why is the entity ID not normalised?

It is an identifier, not a page address. Re-serialising it would add a trailing slash and stop matching the value the IdP has registered.

Where is the certificate?

Not here. A signing certificate comes from your keystore and its format varies; the page emits the descriptor and leaves the key material to you.

Do both signing flags always match?

On this page they do. They are one control because a service provider that signs requests and accepts unsigned assertions is the unusual case.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.