Windows 10
- ID4023: The encrypted security token was directly encrypted using an asymmetric key, which is not supported. An xenc:EncryptedKey ...
- ID4034: A SamlAttributeStatement can only have one SamlAttributeValue of type 'Actor'. This special SamlAttribute is used ...
- ID4036: The key needed to decrypt the encrypted security token could not be resolved from the following security key identifier ...
- ID4037: The key needed to verify the signature could not be resolved from the following security key identifier '{0}'. Ensure ...
- ID4039: A custom ServiceAuthorizationManager has been configured. Any custom ServiceAuthorizationManager must be derived ...
- ID4040: Cannot instantiate a MembershipUserNameSecurityTokenHandler because there is no default MembershipProvider configured ...
- ID4041: Cannot configure the ServiceHost '{0}'. Try calling FederatedServiceCredentials.ConfigureServiceHost before ServiceHost.Open. ...
- ID4046: The SecurityTokenHandler cannot write the token '{0}'. The SecurityTokenHandler can only write tokens of type '{1}'. ...
- ID4051: Cannot resolve SecurityToken. Use config to ensure that a SecurityTokenHandler is registered for token of type '{0}'. ...
- ID4052: SecurityTokenElement cannot create a subject unless it is constructed with an XmlElement and SecurityTokenHandlerCollection. ...
- ID4056: A WindowsClaimsIdentity was not found in this instance of the WindowsClaimsPrincipal. The Identity cannot be accessed ...
- ID4064: Custom configuration provided for MembershipUserNameSecurityTokenHandler does not specify a valid MembershipProvider ...
- ID4066: Cannot read SecurityToken. Expected element ({0}, {1}) with '{2}' attribute set to '{3}'. But the attribute value ...
- ID4070: The X.509 certificate '{0}' chain building failed. The certificate that was used has a trust chain that cannot be ...
- ID4076: SAML Assertion with MajorVersion '{0}' and MinorVersion '{1}' is not supported. The supported version is MajorVersion ...
- ID4078: SAML Assertion does not have any SAML Statement elements. SAML Assertion must have at least one SAML Statement element. ...
- ID4082: SAML Assertion is not valid. XmlReader was expected to reference ('{0}', '{1}') but was referencing ('{2}', '{3}'). ...
- ID4102: An element of an unexpected type was encountered. To support extended types in SAML2 assertions, extend Saml2SecurityTokenHandler. ...
- ID4104: An abstract element was encountered which does not specify its concrete type. Element name: '{0}' Element namespace: ...
- ID4105: A element was encountered which specified an unrecognized concrete type. To handle this custom statement, extend ...
- ID4107: The Saml2Assertion Statements collection contains an unrecognized Saml2Statement. To handle custom Saml2Statement ...
- ID4110: A contained a element which specified an unrecognized concrete type. To handle this custom type, extend Saml2SecurityTokenHandler ...
- ID4112: A element of an unexpected type was encountered. The SubjectConfirmationDataType and KeyInfoConfirmationDataType ...
- ID4113: A was encountered which specifies an unrecognized concrete type. To handle a custom Condition, extend Saml2SecurityTokenHandler ...
- ID4114: A contained unrecognized content. The schema allows arbitrary XML elements on this element without explicit schema ...
- ID4117: When writing the Saml2AuthenticationContext, at least one of ClassReference and DeclarationReference must be set. ...
- ID4118: A element was encountered. To handle by-value authentication context declarations, extend Saml2SecurityTokenHandler ...
- ID4119: The SAML2:AuthenticationStatement, AttributeStatement, and AuthorizationDecisionStatement require a SAML2:Subject. ...
- ID4123: An unrecognized value was encountered for the SAML2:AuthorizationDecisionStatement element's Decision attribute: ...
- ID4126: To handle references for SAML2 assertions, extend Saml2SecurityTokenHandler and override ReadKeyIdentifierClause. ...
- ID4129: Cannot write a SAML2 key identifier clause with an implied derived key length other than the default of 32 using ...
- ID4133: A Saml2SecurityToken cannot be created from the Saml2Assertion because it specifies the Bearer confirmation method ...
- ID4134: A Saml2SecurityToken cannot be created from the Saml2Assertion because it specifies the Holder-of-key confirmation ...
- ID4136: A Saml2SecurityToken cannot be created from the Saml2Assertion because it specifies an unsupported confirmation method: ...
- ID4138: No suitable Saml2NameIdentifier could be created for the SAML2:Assertion because tokenDescriptor.Issuer is null or ...
- ID4139: No suitable Saml2NameIdentifier could be created for the SAML2:Subject because more than one Claim of type NameIdentifier ...
- ID4140: This Assertion cannot be re-emitted as raw XML. This may be because it was not read from XML in the first place, ...
- ID4141: The SAML2:Assertion is not signed. Only signed Assertions are acceptable for this use. If Windows Identity Foundation ...
- ID4142: The SAML2:Assertion is signed but the signature's KeyIdentifier cannot be resolved to a SecurityToken. Ensure that ...
- ID4147: The Saml2SecurityToken is rejected because the SAML2:Assertion's NotBefore condition is not satisfied. NotBefore: ...
- ID4148: The Saml2SecurityToken is rejected because the SAML2:Assertion's NotOnOrAfter condition is not satisfied. NotOnOrAfter: ...
- ID4149: The Saml2SecurityToken is rejected because the SAML2:Assertion specifies a OneTimeUse condition. Enforcement of the ...
- ID4150: The Saml2SecurityToken is rejected because the SAML2:Assertion specifies a ProxyRestriction condition. Enforcement ...
- ID4152: The Saml2SecurityToken cannot be validated because the IssuerToken property is not set. Unsigned SAML2:Assertions ...
- ID4153: A Saml2SecurityToken cannot be created from the Saml2Assertion because it contains a SubjectConfirmationData which ...
- ID4154: A Saml2SecurityToken cannot be created from the Saml2Assertion because it contains a SubjectConfirmationData which ...
- ID4157: A Saml2SecurityToken cannot be created from the Saml2Assertion because it contains a SubjectConfirmationData which ...
- ID4158: A was encountered while processing the attribute statement. To handle encrypted attributes, extend the Saml2SecurityTokenHandler ...
- ID4161: The reader is not positioned on an element that can be read. Call CanReadKeyIdentifierClause to check the element ...
- ID4162: The Saml2SecurityTokenHandler can only write SecurityKeyIdentifierClause objects of type Saml2AssertionKeyIdentifierClause. ...
- ID4174: Cannot create a ClaimsPrincipal from this HTTP context because the issuer of the X.509 client certificate was not ...
- ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this ...
- ID4176: The Saml2SecurityToken is rejected because the SAML2:Assertion's SubjectConfirmationData NotBefore is not satisfied. ...
- ID4177: The Saml2SecurityToken is rejected because the SAML2:Assertion's SubjectConfirmationData NotOnOrAfter is not satisfied. ...
- ID4178: The EncryptingCredentials provided in the SecurityTokenDescriptor is for an asymmetric key. You must use an EncryptedKeyEncryptingCredentials ...
- ID4179: The EncryptingCredentials provided in the Scope must be an asymmetric key. You must set an X509EncryptingCredentials ...
- ID4180: A SAML2 assertion that specifies an AuthenticationContext DeclarationReference is not supported. To handle DeclarationReference, ...
- ID4184: The EncryptingCredentials provided in the SecurityTokenDescriptor must not be null if Scope.TokenEncryptionRequired ...
- ID4185: A Saml2SecurityToken cannot be created from the AuthenticationMethod Claim value, '{0}', which will be serialized ...
- ID4189: The reader is not positioned on a DataReference. XmlEnc specifies that once a DataReference is found only a DataReference ...
- ID4190: The reader is not positioned on a KeyReference. XmlEnc specifies that once a KeyReference is found only a KeyReference ...
- ID4218: A Saml2SamlAttributeStatement can only have one Saml2Attribute of type 'Actor'. This special Saml2Attribute is used ...
- ID4220: The SAML Assertion is either not signed or the signature's KeyIdentifier cannot be resolved to a SecurityToken. Ensure ...
- ID4221: Cannot write SAML Signature KeyIdentifier '{0}'. For custom clause override Saml11SecurityTokenHandler.WriteSigningKeyInfo. ...
- ID4222: The SamlSecurityToken is rejected because the SamlAssertion.NotBefore condition is not satisfied. NotBefore: '{0}' ...
- ID4223: The SamlSecurityToken is rejected because the SamlAssertion.NotOnOrAfter condition is not satisfied. NotOnOrAfter: ...
- ID4225: The SamlSubject '{0}' is different than the SamlSubject present inside another SamlStatement of this SamlAssertion. ...
- ID4240: The tokenRequirement must derived from 'RecipientServiceModelSecurityTokenRequirement' for SecureConversationSecurityTokens. ...
- ID4243: Could not create a SecurityToken. A token was not found in the token cache and no cookie was found in the context. ...
- ID4254: The AttributeValueXsiType of a SAML Attribute must be a string of the form 'prefix#suffix', where prefix and suffix ...
- ID4255: The SecurityToken is rejected because the validation time is out of range. ValidTo: '{0}' ValidFrom: '{1}' Current ...
- ID4261: X509SecurityTokenHandler can serialize SecurityKeyIdentifierClauses only when the property WriteXmlDSigDefinedClauseTypes ...
- ID4267: IdentityModelServiceAuthorizationManager is being used in a incorrect configuration. The ServiceCredentials type ...
- ID4272: The Configuration property of this SecurityTokenHandler is set to null. Tokens cannot be processed in this state. ...
- ID4273: SessionSecurityTokenCookieSerializer.BootstrapTokenHandler is set to null. Bootstrap tokens in the SessionSecurityToken ...