Static ReadonlyNAMESPACEThe WSDL's target namespace, and its WS-MEX section's identifier.
StaticacceptsWhether a request may carry encryption the WSDL offers: the realm
accepts ciphertext no map names (wstrust.acceptEncryptedElements,
off by default), and its encryption certificate holds an RSA key, which
both suites' key transport needs.
true when both hold
StaticdocumentThe WSDL for one base URL, one issuer and one set of flags.
the realm's base URL, no trailing slash
the issuer every token from this STS names
which alternatives the running service accepts
the document
StaticencryptionThe realm's XML Encryption certificate, base64 DER: the first that
helpers.ownXmlEncryptionCertificates() lists, the one its SAML
metadata offers and crypto.decryptElement() opens with. Read when the
document is drawn, so a rotation is in the next one (served no-store).
the certificate, or '' when there is none yet
StaticliveThe flags document reads, as the endpoint reads them: Kerberos through
Krb5Tokens.settingOn, the client certificate off only when the setting
is exactly false, and the empty alternative only while credentials are
not verified.
the flags
StaticresponseWhich suite the service-wide response cipher is: sp:Basic256Sha256's
AES-256-CBC with RSA-OAEP-MGF1P, or the IYA-STS suite's AES-256-GCM with
RSA-OAEP over SHA-256 (WsEncryption.effectiveTransport(), which turns
rsa-oaep-mgf1p into rsa-oaep where legacy hashes are refused). An
application's own cipher is not the document's: it is one document for
every application.
'basic256sha256', 'iya', or '' for neither
StaticsendAnswers GET /sts/metadata from the request's base and the flags the
process is running with.
the request
the response
StaticsendAnswers GET /sts/metadata/capabilities: the token capability document
for the request's base and the live flags.
the request
the response
StaticsendAnswers GET /sts/metadata/capabilities.xsd, the extension's schema.
the request
the response
StaticsuiteThe IYA-STS algorithm suite's schema: one empty assertion, in the
manner of WS-SecurityPolicy 1.2's own (sp:QNameAssertionType), for a
validator to read beside the published ones. Not served: the suite is
named, and its algorithms listed, in docs/v1.1.0/ws-trust.md.
the XSD
The WSDL a client reads before it sends a RequestSecurityToken (#958).
A static utility: the route in
wstrust.tscallssend, and a test callsdocumentwith the flags it wants to see.