MCPcopy Create free account

hub / github.com/crewjam/saml / functions

Functions2,436 in github.com/crewjam/saml

FunctionTestSpecCore_2_5_1_5_OneTimeUseIsValidAndExposed
saml-core §2.5.1.5 (lines 962-963): "For the purposes of determining the validity of the <Conditions> element, the <OneTimeUse> is considered to alway
spec_core_assertions_test.go:565
FunctionTestSpecCore_2_5_1_6_ProxyRestrictionIsValidAndExposed
saml-core §2.5.1.6 (lines 994-996): "For the purposes of determining the validity of the <Conditions> element, the <ProxyRestriction> condition is con
spec_core_assertions_test.go:578
FunctionTestSpecCore_2_6_1_AdviceMayBeIgnored
saml-core §2.6.1 (lines 1015-1017): "This information MAY be ignored by applications without affecting either the semantics or the validity of the ass
spec_core_assertions_test.go:594
FunctionTestSpecCore_2_7_3_1_1_EmptyValueSerializedAsEmptyElement
saml-core §2.7.3.1.1 (lines 1246-1247): "If a SAML attribute includes an empty value, such as the empty string, the corresponding <AttributeValue> ele
spec_core_assertions_test.go:643
FunctionTestSpecCore_2_7_3_1_AttributeValuesPreserved
saml-core §2.7.3.1 (lines 1193-1217): an <Attribute> has a Name, an optional NameFormat and FriendlyName, and any number of <AttributeValue> elements,
spec_core_assertions_test.go:611
FunctionTestSpecCore_2_7_3_1_GetByNameIgnoresFriendlyName
saml-core §2.7.3.1: FriendlyName "MUST NOT be used as a basis for formally identifying SAML attributes". AssertionAttributes.GetByName matches the Nam
attributes_by_name_test.go:14
FunctionTestSpecCore_2_7_3_1_KeyAttributesByName
saml-core §2.7.3.1 (line 1204): FriendlyName's "value MUST NOT be used as a basis for formally identifying SAML attributes" (errata E49: they are iden
samlsp/attributes_by_name_test.go:18
FunctionTestSpecCore_4_1_2_AssertionAndResponseVersion
saml-core §4.1.2 (lines 2774-2775): "A SAML relying party MUST NOT process any assertion with a major assertion version number not supported by the re
spec_core_assertions_test.go:654
FunctionTestSpecCore_4_1_3_1_LogoutMessageVersionAndID
saml-core §4.1.3.1 (line 2802): "A SAML responder MUST reject any request with a major request version number not supported by the responder", and §3.
spec_core_assertions_test.go:706
FunctionTestSpecCore_4_1_3_1_RequestVersion
saml-core §4.1.3.1 (lines 2800-2803): "A SAML requester MUST NOT issue a request message with an overall Major.Minor request version number matching a
spec_core_assertions_test.go:739
FunctionTestSpecCore_8_2_GeneratedURIAttributeNamesAreAbsolute
saml-core §8.2.2 (URI reference attribute name format): with NameFormat urn:oasis:names:tc:SAML:2.0:attrname-format:uri the Name is a URI reference. T
spec_core_assertions_test.go:785
FunctionTestSpecCore_8_3_6_IssuerEntityFormatOmitsQualifiers
saml-core §8.3.6 (entity identifier): "The NameQualifier, SPNameQualifier, and SPProvidedID attributes MUST be omitted." The Issuer of the IdP's asser
spec_core_assertions_test.go:770
FunctionTestSpecCore_8_3_NameIDFormatIdentifiers
saml-core §8.3 (lines 3275-3362) and errata E60 (§2.2.2, errata line 507: the unspecified format is urn:oasis:names:tc:SAML:1.1:nameid-format:unspecif
spec_core_assertions_test.go:760
FunctionTestSpecMetadata_2_2_2_EndpointSelectedByBinding
saml-metadata-2.0-os §2.2.2 (lines 229-237): EndpointType carries Binding, Location and an optional ResponseLocation. Profiles §4.1.6 (lines 618-620)
spec_metadata_test.go:370
FunctionTestSpecMetadata_2_2_3_DefaultEndpointIsFirstWithIsDefaultTrue
saml-metadata-2.0-os §2.2.3 (lines 272-273): "the default endpoint is the first such endpoint with the isDefault attribute set to true." Core §3.4.1 (
spec_metadata_test.go:312
FunctionTestSpecMetadata_2_2_3_DefaultEndpointWithoutIsDefaultIsFirst
saml-metadata-2.0-os §2.2.3 (lines 269-275): isDefault is optional and assumed false when omitted; if no endpoint is marked default, the first one is
spec_metadata_test.go:328
FunctionTestSpecMetadata_2_2_3_EndpointSelectedByIndex
saml-metadata-2.0-os §2.2.3 (lines 264-266) and profiles §4.1.6 (lines 629-632): the index attribute distinguishes ACS endpoints that "may be specifie
spec_metadata_test.go:351
FunctionTestSpecMetadata_2_2_3_IsDefaultFalseIsNotTheDefault
saml-metadata §2.2.3 (lines 272-275): when no endpoint has isDefault set to true, "the default endpoint is the first such endpoint without the isDefau
spec_profiles_test.go:157
FunctionTestSpecMetadata_2_2_4_LocalizedNameUsesXMLLang
saml-metadata-2.0-os §2.2.4 and §2.2.5 (lines 285-305): localizedNameType and localizedURIType carry a required xml:lang attribute, in the XML namespa
spec_metadata_test.go:395
FunctionTestSpecMetadata_2_3_2_IdPRootHasValidUntilOrCacheDuration
saml-metadata-2.0-os §2.3.2 (lines 406-407): "When used as the root element of a metadata instance, this element MUST contain either a validUntil or c
spec_metadata_test.go:53
FunctionTestSpecMetadata_2_3_2_MiddlewareMetadataRoot
saml-metadata-2.0-os §2.3.2 (lines 406-407): the root EntityDescriptor of a metadata instance MUST contain either a validUntil or a cacheDuration attr
samlsp/spec_metadata_test.go:82
FunctionTestSpecMetadata_2_3_2_SPRootHasValidUntilOrCacheDuration
saml-metadata-2.0-os §2.3.2 (lines 406-407): the root EntityDescriptor MUST contain either a validUntil or a cacheDuration attribute. The SP metadata
spec_metadata_test.go:75
FunctionTestSpecMetadata_2_3_ParseMetadataRootElements
saml-metadata-2.0-os §2.3 (lines 307-309): a metadata instance has either an <EntityDescriptor> or an <EntitiesDescriptor> root. ParseMetadata accepts
samlsp/spec_metadata_test.go:56
FunctionTestSpecMetadata_2_4_1_1_EncryptionKeySelectionByUse
saml-metadata-2.0-os §2.4.1.1 (lines 612-617) and profiles §4.1.6 (lines 626-628): keys used to receive encryption keys are documented with use="encry
spec_metadata_test.go:278
FunctionTestSpecMetadata_2_4_1_1_GeneratedKeyDescriptorUseValues
saml-metadata-2.0-os §2.4.1.1 (lines 615-617, 636-641): the use attribute of a KeyDescriptor is optional and its values are drawn from the KeyTypes en
spec_metadata_test.go:212
FunctionTestSpecMetadata_2_4_1_1_SigningKeySelectionByUse
saml-metadata-2.0-os §2.4.1.1 (lines 615-617): use is optional; a key without it is not restricted to one purpose. Profiles §4.1.6 (lines 625-626): si
spec_metadata_test.go:240
FunctionTestSpecMetadata_2_4_1_ProtocolSupportEnumerationIncludesSAML2
saml-metadata-2.0-os §2.4.1 (lines 563-566): protocolSupportEnumeration is required, and "For SAML V2.0 entities, this set MUST include the SAML proto
spec_metadata_test.go:98
FunctionTestSpecMetadata_2_4_2_SPArtifactResolutionServiceIsIndexed
saml-metadata-2.0-os §2.4.2 (lines 648-651) and §2.2.3: the ArtifactResolutionService of an SPSSODescriptor is an indexed endpoint; its index and isDe
spec_metadata_test.go:529
FunctionTestSpecMetadata_2_4_3_IdPSingleSignOnServiceHasNoResponseLocation
saml-metadata-2.0-os §2.4.3 (lines 690-693): an IDPSSODescriptor has one or more SingleSignOnService elements, and "The ResponseLocation attribute MUS
spec_metadata_test.go:122
FunctionTestSpecMetadata_2_4_4_SPAssertionConsumerServicesAreIndexed
saml-metadata-2.0-os §2.4.4 (lines 748-751) and §2.2.3 (lines 264-268): an SPSSODescriptor has one or more AssertionConsumerService elements, each an
spec_metadata_test.go:142
FunctionTestSpecMetadata_2_4_4_SPAuthnRequestsSignedMatchesSigning
saml-metadata-2.0-os §2.4.4 (lines 740-742): AuthnRequestsSigned "indicates whether the <samlp:AuthnRequest> messages sent by this service provider wi
spec_metadata_test.go:169
FunctionTestSpecMetadata_3_1_2_SignatureReferencesExistingID
saml-metadata-2.0-os §3.1.2 (lines 1185-1190): "Signed metadata elements MUST supply a value for the identifier attribute on the signed element." An I
spec_metadata_test.go:487
FunctionTestSpecMetadata_3_1_SignedMetadataProfile
saml-metadata-2.0-os §3.1 (lines 1181-1207): signed metadata uses an enveloped signature (1181); the signed element supplies an identifier attribute (
spec_metadata_test.go:428
FunctionTestSpecMetadata_4_1_1_MetadataContentType
saml-metadata-2.0-os §4.1.1 (lines 1234-1235): "If the publishing protocol permits MIME-based identification of content types, the content type of the
spec_metadata_test.go:508
FunctionTestSpecMetadata_4_3_2_FetchMetadataFollowsRedirects
Tests in this file pin behavior required by the OASIS SAML V2.0 Metadata specification (saml-metadata-2.0-os). saml-metadata-2.0-os §4.3.2 (lines 1407
samlsp/spec_metadata_test.go:24
FunctionTestSpecProfile_4_1_2_IdPDoesNotSendResponseWithRedirectBinding
saml-profiles §4.1.2 step 5: for the <Response>, "The HTTP Redirect binding MUST NOT be used". The IdP refuses to deliver a Response to an ACS endpoin
spec_profiles_test.go:227
FunctionTestSpecProfile_4_1_2_ResponseNotAcceptedFromQuery
saml-profiles §4.1.2 step 5: "The HTTP Redirect binding MUST NOT be used" to deliver the <Response>. ParseResponse does not take a SAMLResponse from t
spec_profiles_test.go:503
FunctionTestSpecProfile_4_1_3_4_NoAssertionWithoutValidSession
saml-profiles §4.1.3.4: "the identity provider MUST establish the identity of the principal (unless it returns an error to the service provider)". An
samlidp/spec_profiles_test.go:68
FunctionTestSpecProfile_4_1_4_1_AuthnRequestIssuerAndNameIDPolicy
saml-profiles §4.1.4.1: "The <Issuer> element MUST be present and MUST contain the unique identifier of the requesting service provider; the Format at
spec_profiles_test.go:102
FunctionTestSpecProfile_4_1_4_1_IdPVerifiesRequestedACS
saml-profiles §4.1.4.1: "the identity provider MUST ensure that any <AssertionConsumerServiceURL> or <AssertionConsumerServiceIndex> elements in the r
spec_profiles_test.go:119
FunctionTestSpecProfile_4_1_4_2_AuthnStatementRequired
saml-profiles §4.1.4.2 (lines 547-550): "The set of one or more assertions MUST contain at least one <AuthnStatement> that reflects the authentication
spec_profiles_test.go:422
FunctionTestSpecProfile_4_1_4_2_ErrorStatusIsNotAccepted
saml-profiles §4.1.4.2: "If the identity provider wishes to return an error, it MUST NOT include any assertions in the <Response> message." The SP doe
spec_profiles_test.go:464
FunctionTestSpecProfile_4_1_4_2_IdPResponseContents
saml-profiles §4.1.4.2 (<Response> Usage), for a response the IdP makes: - the Response Issuer, if present, and each assertion Issuer contain the IdP'
spec_profiles_test.go:257
FunctionTestSpecProfile_4_1_4_2_IssuerMustBeTheIdP
saml-profiles §4.1.4.2: "The <Issuer> element MAY be omitted, but if present it MUST contain the unique identifier of the issuing identity provider" a
spec_profiles_test.go:448
FunctionTestSpecProfile_4_1_4_2_SessionIndexForSingleLogout
saml-profiles §4.1.4.2: "If the identity provider supports the Single Logout profile, defined in Section 4.4, any such authentication statements MUST
samlidp/spec_profiles_test.go:45
FunctionTestSpecProfile_4_1_4_3_ACSRejectsUntrackedResponse
saml-profiles §4.1.4.3: the SP MUST "Verify that the InResponseTo attribute in the bearer <SubjectConfirmationData> equals the ID of its original <Aut
samlsp/spec_profiles_test.go:52
FunctionTestSpecProfile_4_1_4_3_InResponseToMustMatchRequest
saml-profiles §4.1.4.3: the SP MUST "Verify that the InResponseTo attribute in the bearer <SubjectConfirmationData> equals the ID of its original <Aut
spec_profiles_test.go:370
FunctionTestSpecProfile_4_1_4_3_RecipientMustMatchACS
saml-profiles §4.1.4.3: the SP MUST "Verify that the Recipient attribute in any bearer <SubjectConfirmationData> matches the assertion consumer servic
spec_profiles_test.go:330
FunctionTestSpecProfile_4_1_4_3_SessionNotOnOrAfterEndsSession
saml-profiles §4.1.4.3 (lines 588-591): "If an <AuthnStatement> used to establish a security context for the principal contains a SessionNotOnOrAfter
samlsp/spec_profiles_test.go:169
FunctionTestSpecProfile_4_1_4_3_SubjectConfirmationNotOnOrAfter
saml-profiles §4.1.4.3: the SP MUST "Verify that the NotOnOrAfter attribute in any bearer <SubjectConfirmationData> has not passed, subject to allowab
spec_profiles_test.go:351
FunctionTestSpecProfile_4_1_4_5_ReplayCacheOption
saml-profiles §4.1.4.5: "The service provider MUST ensure that bearer assertions are not replayed, by maintaining the set of used ID values for the le
samlsp/spec_profiles_test.go:31
FunctionTestSpecProfile_4_1_4_5_UnsignedOrUntrustedAssertionRejected
saml-profiles §4.1.4.5: "If the HTTP POST binding is used to deliver the <Response>, the enclosed assertion(s) MUST be signed." and §4.1.4.3 "Verify a
spec_profiles_test.go:479
FunctionTestSpecProfile_4_1_5_IdPInitiatedUsesDefaultACS
saml-profiles §4.1.5 (lines 609-611): an unsolicited "<Response> or artifact SHOULD be delivered to the <md:AssertionConsumerService> endpoint of the
spec_profiles_test.go:190
FunctionTestSpecProfile_4_1_5_IdPUnsolicitedResponseHasNoInResponseTo
saml-profiles §4.1.5: "An unsolicited <Response> MUST NOT contain an InResponseTo attribute, nor should any bearer <SubjectConfirmationData> elements
spec_profiles_test.go:312
FunctionTestSpecProfile_4_1_5_UnsolicitedResponses
saml-profiles §4.1.5: an unsolicited Response has no InResponseTo, and §4.1.4.3 says that for an unsolicited response "the attribute MUST NOT be prese
spec_profiles_test.go:396
FunctionTestSpecProfile_4_1_6_IdPUsesDefaultACSWhenUnspecified
saml-profiles §4.1.6: "The isDefault attribute is used to specify the endpoint to use if not specified in a request."
spec_profiles_test.go:137
FunctionTestSpecProfile_4_4_3_1_SignLogoutOption
saml-profiles §4.4.3.1: "The <LogoutRequest> message MUST be signed if the HTTP POST or Redirect binding is used." Options.SignLogout signs the middle
samlsp/spec_profiles_test.go:140
FunctionTestSpecProfile_4_4_3_1_SignedLogoutRequestWithSessionIndex
saml-profiles §4.4.3.1: "The <LogoutRequest> message MUST be signed if the HTTP POST or Redirect binding is used", and the session participant issues
samlsp/spec_profiles_test.go:84
FunctionTestSpecProfile_4_4_3_4_SignedLogoutResponseToIdP
saml-profiles §4.4.3.4: the session participant "MUST issue a <LogoutResponse> message ... to the requesting identity provider", which "MUST be signed
samlsp/spec_profiles_test.go:114
FunctionTestSpecProfile_4_4_3_LogoutSignatureMethodSignsOnlyLogout
saml-profiles §4.4.3.1 and §4.4.3.4: the LogoutRequest and LogoutResponse "MUST be signed if the HTTP POST or Redirect binding is used". With LogoutSi
spec_profiles_test.go:740
FunctionTestSpecProfile_4_4_4_1_IdPRejectsUnsignedLogoutRequest
saml-profiles §4.4.3.1 / §4.4.4.1: "The <LogoutRequest> message MUST be signed if the HTTP POST or Redirect binding is used". The IdP refuses an unsig
spec_profiles_test.go:651
FunctionTestSpecProfile_4_4_4_1_SPLogoutRequest
saml-profiles §4.4.4.1: the LogoutRequest "<Issuer> element MUST be present and MUST contain the unique identifier of the requesting entity; the Forma
spec_profiles_test.go:521
FunctionTestSpecProfile_4_4_4_1_SPRejectsUnauthenticatedLogoutRequest
saml-profiles §4.4.4.1: "The requester MUST authenticate itself to the responder and ensure message integrity" and the Issuer "MUST be present". The S
spec_profiles_test.go:584
FunctionTestSpecProfile_4_4_4_2_IdPLogoutResponse
saml-profiles §4.4.4.2 and §4.4.3.5: the IdP answers a LogoutRequest with a LogoutResponse whose Issuer is present and names the IdP (Format omitted o
spec_profiles_test.go:624
FunctionTestSpecProfile_4_4_4_2_SPLogoutResponse
saml-profiles §4.4.4.2: the LogoutResponse "<Issuer> element MUST be present and MUST contain the unique identifier of the responding entity". §4.4.3.
spec_profiles_test.go:542
FunctionTestSpecProfile_4_4_4_2_SPRejectsUnauthenticatedLogoutResponse
saml-profiles §4.4.4.2: "The responder MUST authenticate itself to the requester and ensure message integrity" and the Issuer "MUST be present". The S
spec_profiles_test.go:607
FunctionTestSpecProfile_5_4_1_ArtifactResolveIssuer
saml-profiles §5.4.1: the ArtifactResolve "<Issuer> element MUST be present and MUST contain the unique identifier of the requesting entity; the Forma
spec_profiles_test.go:663
FunctionTestSpecProfile_6_4_1_AttributeQueryIssuer
saml-profiles §6.4.1: for the Assertion Query/Request profile "The <Issuer> element MUST be present", and §6.3.1 "The requester SHOULD authenticate it
spec_profiles_test.go:673
FunctionTestSpecProfile_8_AttributeProfilesNameFormatAndType
saml-profiles §8.1.4 (Basic Attribute Profile): "The xsi:type attribute MUST be present and be given the appropriate value." §8.1.2: the NameFormat MU
spec_profiles_test.go:689
FunctionTestSpecProtocol_3_2_1_AuthnRequestIDRequired
saml-core-2.0-os §3.2.1 (lines 1467-1470): ID is "[Required]", and "the values of the ID attribute in a request and the InResponseTo attribute in the
spec_core_protocols_test.go:132
FunctionTestSpecProtocol_3_2_1_DestinationMismatchDiscarded
saml-core-2.0-os §3.2.1 (Destination): "If it is present, the actual recipient MUST check that the URI reference identifies the location at which the
spec_core_protocols_test.go:108
FunctionTestSpecProtocol_3_2_1_LogoutRequestIDRequired
saml-core-2.0-os §3.2.1: "ID [Required] An identifier for the request", whose value the response's InResponseTo must match. The IdP rejects a (validly
spec_core_protocols_test.go:290
FunctionTestSpecProtocol_3_2_2_2_SPRejectsNonSuccessTopLevelStatus
saml-core-2.0-os §3.2.2.2 and §3.4.1.4: an error Response carries a top-level code (here Responder) and optionally a second-level one (here NoPassive)
spec_core_protocols_test.go:272
FunctionTestSpecProtocol_3_2_2_2_StatusCodeNesting
saml-core-2.0-os §3.2.2.2: "The value of the topmost <StatusCode> element MUST be from the top-level list"; a second-level code is a <StatusCode> nest
spec_core_protocols_test.go:247
FunctionTestSpecProtocol_3_2_2_ResponseIDsAreUnique
saml-core-2.0-os §3.2.2: the Response ID "MUST follow the requirements specified in Section 1.3.4 for identifier uniqueness". Two responses (and their
spec_core_protocols_test.go:94
FunctionTestSpecProtocol_3_2_2_ResponseRequiredAttributes
saml-core-2.0-os §3.2.2 (StatusResponseType): ID, Version ("2.0") and IssueInstant are required, and InResponseTo "MUST be present and its value MUST
spec_core_protocols_test.go:55
FunctionTestSpecProtocol_3_2_2_UnsolicitedResponseOmitsInResponseTo
saml-core-2.0-os §3.2.2: "If the response is not generated in response to a request ... then this attribute [InResponseTo] MUST NOT be present." An Id
spec_core_protocols_test.go:77
FunctionTestSpecProtocol_3_4_1_2_ProxyCountZeroIsSerialized
saml-core-2.0-os §3.4.1.2: ProxyCount "A count of zero permits no proxying, while omitting this attribute expresses no such restriction." A ProxyCount
spec_core_protocols_test.go:227
FunctionTestSpecProtocol_3_4_1_4_AssertionContents
saml-core-2.0-os §3.4.1.4: the returned assertion "MUST contain a <saml:Subject> element that represents the presenter", at least one statement "MUST
spec_core_protocols_test.go:159
FunctionTestSpecProtocol_3_4_1_SPAuthnRequestAttributes
saml-core-2.0-os §3.2.1 (ID, Version, IssueInstant [Required]), §3.4.1 and §3.4.1.1: the SP's AuthnRequest carries the required attributes and an Issu
spec_core_protocols_test.go:192
FunctionTestSpecProtocol_3_7_1_NotOnOrAfterAllowsClockSkew
saml-core-2.0-os §3.7.1 NotOnOrAfter, as amended by errata E92: "relying parties SHOULD allow for reasonable clock skew in the interpretation of both
spec_core_protocols_test.go:327
FunctionTestSpecProtocol_3_7_1_SPLogoutRequestShape
saml-core-2.0-os §3.7.1 and §3.2.1: the SP's LogoutRequest has the required ID, Version and IssueInstant, an Issuer, the principal's <saml:NameID> ("[
spec_core_protocols_test.go:381
FunctionTestSpecProtocol_3_7_2_IdPLogoutResponseAttributes
saml-core-2.0-os §3.7.2: "The recipient of a <LogoutRequest> message MUST respond with a <LogoutResponse> message, of type StatusResponseType"; per §3
spec_core_protocols_test.go:304
FunctionTestSpecProtocol_3_7_2_SPLogoutResponseAnswersRequest
saml-core-2.0-os §3.7.2 and §3.2.2: the LogoutResponse the SP sends to answer the IdP's LogoutRequest has InResponseTo set to the request's ID, the re
spec_core_protocols_test.go:404
FunctionTestSpecProtocol_3_7_3_2_SPAcceptsSuccessWithPartialLogout
saml-core-2.0-os §3.7.3.2: "the top-level status indicates the state of the logout operation only with respect to the session authority itself"; incom
spec_core_protocols_test.go:364
FunctionTestSpecSig_5_3_UnsignedAssertionInheritsResponseSignature
saml-core-2.0-os §5.3 (lines 2899-2906): an assertion without its own ds:Signature inherits the signature of the enclosing Response when that signatur
spec_signature_encryption_test.go:288
FunctionTestSpecSig_5_3_UnsignedAssertionWithoutEnclosingSignatureRejected
saml-core-2.0-os §5.3 (lines 2899-2906) read with §5 (lines 2883-2884): inheritance needs an enclosing signature. An unsigned assertion in an unsigned
spec_signature_encryption_test.go:308
FunctionTestSpecSig_5_4_2_ChangedIDBreaksSignature
saml-core-2.0-os §5.4.2 (lines 2929-2935): the signature is bound to the ID of the element it is enveloped in. Changing the ID of a signed assertion (
spec_signature_encryption_test.go:332
FunctionTestSpecSig_5_4_2_ReferenceToOtherIDRejected
saml-core-2.0-os §5.4.2 (lines 2933-2935): "Signatures MUST contain a single <ds:Reference> containing a same-document reference to the ID attribute v
spec_signature_encryption_test.go:319
FunctionTestSpecSig_5_4_2_SignatureWrappingRejected
Signature wrapping, saml-core-2.0-os §5.4.2 (lines 2933-2935) and §2.3.3 (lines 597-599: "If it is invalid, then the relying party MUST NOT rely on th
spec_signature_encryption_test.go:462
FunctionTestSpecSig_5_4_3_ExclusiveC14NWithCommentsAccepted
saml-core-2.0-os §5.4.3 (lines 2937-2940) allows Exclusive Canonicalization "with or without comments"; §5.4.4 (lines 2944-2945) lists xml-exc-c14n#Wi
spec_signature_encryption_test.go:364
FunctionTestSpecSig_5_4_4_ContentExcludingTransformsRejected
saml-core-2.0-os §5.4.4 (lines 2942-2950): verifiers "MAY reject signatures that contain other transform algorithms as invalid. If they do not, verifi
spec_signature_encryption_test.go:346
FunctionTestSpecSig_5_4_5_KeyInfoCertificateMustBeTrustedForSigning
saml-core-2.0-os §5.4.5 (lines 2951-2954) places no restriction on KeyInfo, so its contents are not a trust anchor: a signature that verifies under th
spec_signature_encryption_test.go:400
FunctionTestSpecSig_5_4_5_KeyInfoMayBeAbsent
saml-core-2.0-os §5.4.5 (lines 2951-2954): "SAML does not require the use of <ds:KeyInfo> ... Therefore, <ds:KeyInfo> MAY be absent." A signature with
spec_signature_encryption_test.go:387
FunctionTestSpecSig_5_4_IdPSignaturesFollowProfile
saml-core-2.0-os §5.4.1 (lines 2925-2926): "SAML assertions and protocols MUST use enveloped signatures"; §5.4.2 (lines 2933-2935): a single Reference
spec_signature_encryption_test.go:233
FunctionTestSpecSig_5_4_SPRequestSignaturesFollowProfile
saml-core-2.0-os §5.4 (lines 2925-2935) and §5.2 (line 2897): requests the SP signs (AuthnRequest, LogoutRequest, ArtifactResolve) carry one enveloped
spec_signature_encryption_test.go:252
FunctionTestSpecSig_6_2_DecryptThenVerify
saml-core-2.0-os §6.2 (lines 3117-3121): "A relying party MUST perform signature validation and decryption in the reverse order that signing and encry
spec_signature_encryption_test.go:553
FunctionTestSpecSig_6_2_IdPSignsAssertionBeforeEncrypting
saml-core-2.0-os §6.1 (lines 3110-3113): "The <EncryptedData> element's Type attribute SHOULD be used and, if it is present, MUST have the value http:
spec_signature_encryption_test.go:515
FunctionTestSpecSig_6_3_EncryptedKeyBesideEncryptedData
sstc-saml-core-errata-2.0-wd-07 §6.3 [E43] (lines 3290-3297): an EncryptedKey included in the instance SHOULD be referenced from the EncryptedData's K
spec_signature_encryption_test.go:590
FunctionTestSpecSig_Conformance_4_1_MandatorySignatureAlgorithms
saml-conformance-2.0-os §4.1 (lines 237-246): compliant implementations MUST implement the SHA1 digest, Canonical XML (without comments), the envelope
spec_signature_encryption_test.go:430
← previousnext →2,201–2,300 of 2,436, ranked by callers