SAML SP Metadata Builder
Generate SAML 2.0 SP metadata with ACS, optional SLO, NameID format, and signing certificate.
Build SAML 2.0 service provider metadata
A service provider (SP) publishes metadata with its entityID, preferred
NameIDFormat, AssertionConsumerService (ACS) URL for POST bindings, optional
single logout endpoint, and signing certificate for AuthnRequest or assertion decryption policies.
Fill in ACS and entity ID values from your application configuration, adjust NameID format to match what your IdP releases (email, persistent, or transient), and paste an optional SP signing certificate. Related: SAML IdP Metadata Builder, OIDC Discovery Inspector.
Common NameID formats
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressurn:oasis:names:tc:SAML:2.0:nameid-format:persistenturn:oasis:names:tc:SAML:2.0:nameid-format:transient
Frequently Asked Questions
What ACS binding is generated?
HTTP-POST at index 0 with isDefault="true", which is the most common integration pattern
for web applications.
What do AuthnRequestsSigned and WantAssertionsSigned mean?
The template sets AuthnRequestsSigned="false" and WantAssertionsSigned="true".
Edit the XML if your federation requires signed AuthnRequests.
Is metadata generated on your servers?
No. The XML is built client-side only.
Related Tools
Plasma Osmolality Calculator
Watt To Lumen Calculator
Polynomial Regression Calculator
Rainwater Collection Calculator
Charles Law Calculator
Vapor Pressure of Water Calculator
Hardness Conversion Calculator
Child Cost Calculator
iMessage Chat Generator
Validate Clock Time
HTML Preview
CD Calculator
CSS To JS Converter
Random Integer Range Generator
RSA Encrypt Decrypt
JSON To Io TS
Pomodoro Technique
Equilibrium Constant Calculator
Shannon Diversity Index Calculator
Fence Picket Calculator