SAMLSIGN(1)

πŸ’– SAMLSIGN β€” bestie edition πŸ’–

okay so this is the OpenSAML manual page for samlsign, and honestly? it's giving "i sign your XML and i verify your XML and i look cute doing it" ✨


✨ NAME ✨

samlsign β€” sign and verify XML documents πŸ–‹οΈπŸ”


🌸 SYNOPSIS 🌸

samlsign <options>

πŸ¦‹ DESCRIPTION πŸ¦‹

samlsign signs or verifies signed XML documents. no cap, that's the whole job and it's iconic.

Wanna sign a document? use -s. Wanna verify one? literally just omit -s, that's it, that's the vibe.

When you're verifying, one of -c, -R, or -T is required. and when you're signing, either -k or -R is required. no skipping, bestie, the tool will simply not know what you want from it 😭

By default, samlsign signs or verifies standard input. if you'd rather it pull the document from somewhere else, pass -u (URL) or -f (file path) 🫢

And the glow-up: signed documents are always printed to standard output. always always. periodt. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • -u URL β€” the URL of the document you wanna sign or verify 🌐
  • -f PATH β€” the full path of the document you wanna sign or verify πŸ“
  • -id ID β€” instead of acting on the whole entire document, only act on the object with the specified ID. only that one object (with its shiny new signature) gets printed to standard output. main character object energy, lowkey πŸ‘‘
  • -s β€” sign, rather than the default action of verify ✍️
  • -k KEY β€” the full path to the key you're using to sign πŸ”‘
  • -c CERT β€” the full path to the certificate you're using to verify πŸ“œ
  • -R RESOLVER β€” specifies a credential resolver to use, either for signing or for verification 🧰
  • -T TRUST β€” specifies the trust engine for TrustEngine-based verification πŸ›‘οΈ
  • -M METADATA β€” specifies the metadata for TrustEngine-based verification πŸ“š
  • -i ISSUER β€” specifies the issuer for verification 🏷️
  • -p PROT β€” specifies the protocol for TrustEngine-based verification. this one lets you name an arbitrary protocol by name, but honestly you'd more commonly use one of the options listed below for the standard protocol names πŸ’«
  • -r RNAME β€” specifies the resource name for TrustEngine-based verification. again, arbitrary resource name by name is allowed, but you'd more commonly reach for one of the options listed below for the standard resource names πŸ—οΈ
  • -ns RNS β€” specifies the namespace for TrustEngine-based verification. if you don't give one, the default is SAML20MD_NS 🌌
  • -saml10 β€” use the SAML1.0 protocol for TrustEngine-based verification πŸ•°οΈ
  • -saml11 β€” use the SAML1.1 protocol for TrustEngine-based verification πŸ•°οΈ
  • -saml2 β€” use the SAML2.0 P NS protocol for TrustEngine-based verification πŸš€
  • -idp β€” set the resource name to IDPSSODescriptor for TrustEngine-based verification πŸͺͺ
  • -aa β€” set the resource name to AttributeAuthorityDescriptor for TrustEngine-based verification πŸ—‚οΈ
  • -pdp β€” set the resource name to PDPDescriptor for TrustEngine-based verification βš–οΈ
  • -sp β€” set the resource name to SPSSODescriptor for TrustEngine-based verification 🀝
  • -V β€” validate the document while you're signing or verifying it. the path to the schemas used for validation can be overridden by setting the OPENSAML_SCHEMAS environment variable πŸ”¬
  • -alg algorithm β€” specifies the signature algorithm to use, overriding the default. only used when signing ✨
  • -dig algorithm β€” specifies the digest algorithm to use, overriding the default. only used when signing ✨

πŸ’€ EXIT STATUS πŸ’€

  • 0 β€” success πŸŽ‰
  • -1 β€” an error in how samlsign was called (incorrect arguments, for example) πŸ™ˆ
  • -2 β€” an error occurred when initializing the configuration 😡
  • -10 β€” an exception was caught 😭

🌈 EXAMPLES 🌈

To sign SAML 2.0 metadata, use:

samlsign -k /path/to/key -c /path/to/cert -f /path/to/metadata

that's it. that's the whole recipe. slay πŸ“


πŸ‘‘ AUTHOR πŸ‘‘

This manpage were written by Ferenc WÑgner and Russ Allbery for Debian GNU/Linux 🫢


Copyleft (C) 2008 Ferenc WΓ‘gner This is free software in the public domain.


ok bestie that's the whole page, every flag accounted for, not a single detail left behind πŸ’–

and the cute little sign-off at the bottom: this one's from UCAID, dated 2011 Jul 25 🌸 go forth and sign responsibly ✨πŸ’