Service Provider Metadata Reference

This is a reference for Build a Service Provider Metadata File. Each SP metadata .xml file accepts the following elements.Build a Service Provider Metadata File

entityId

Unique identifier or name for the service provider. The ID should be a URN or a URL.

Type

String

Required

Yes

Default

N/A

Example

"https://example.moogsoftaiops.com/moogsvr/mooms"

id

Unique identifier for the root metadata element.

Type

String

Required

No

Default

N/A

Example

"TW9vZ3NvZnRBSU9wcw=="

validUntil

The expiration date of the metadata file. Provide the date in ISO 8601 format.

Type

String

Required

No

Default

N/A

Example

"2018-08-10T07:47:41+00:00"

authnRequestsSigned

If enabled, Moogsoft Enterprise signs SAML authentication requests as part of the Single Sign-On.

Type

Boolean

Required

No

Default

false

wantAssertionsSigned

If enabled, Moogsoft Enterprise expects IdPs to sign any SAML assertions it sends.

Type

Boolean

Required

No

Default

false

keyDescriptor

Defines the type of signing or the type of encryption that Moogsoft Enterprise uses.

Type

String

Required

No

One of

use = "signing", use = "encryption"

x509Certificate

Self-signed certificate that allows Moogsoft Enterprise to sign and encrypt each SAML assertion. The certificate should be in DER format and base-64 encoded.

Type

String

Required

No

Example

MIIDijCCAnICCQD[...]

assertionConsumerService

The URL or endpoint that receives the SAML assertions. The location is for the URL and the binding identifies the method. Supported bindings include HTTP-Artifact, HTTP-POST, HTTP-POST-SimpleSign, HTTP-Redirect and SOAP.

Type

String

Required

Yes

Example

Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST Location="https://localhost/moogsvr/mooms?request=samlResponse"