Windows 10
- ID3025: Cannot read 'RequestedProofToken' element. The 'RequestedProofToken' element must either contain a 'EncryptedKey' ...
- ID3026: Cannot read 'Entropy' element. The 'Entropy' element must either contain a 'EncryptedKey' element or a 'BinarySecret' ...
- ID3027: The key needed to decrypt the encrypted key could not be resolved. Ensure that '{0}' is populated with the required ...
- ID3043: The Mime type '{0}' specified in the 'CardImage' element is not recognized. The valid Mime types are 'image/jpeg', ...
- ID3052: Information Card has a SupportedClaimType whose DisplayTag has length: '{0}'. The length must be between 1 - 255. ...
- ID3053: Information Card has a SupportedClaimType whose Description has length: '{0}'. The length must be between 1 - 255. ...
- ID3060: Information Card contains a X509Credentials type '{0}' which is not supported. The supported clause types are X5 ...
- ID3062: Unrecognized credentials type. Must be one of UsernamePasswordCredential, KerberosV5Credential, X509V3Credentials ...
- ID3080: Information Card contains a X509Credentials with an Thumbprint clause but the EncodingType '{0}' is not supported. ...
- ID3092: The specified UseKey '{0}' cannot be resolved to a token that would prove the client's possession of the private ...
- ID3095: Cannot create WS-Federation message from the given HttpRequest. Check if the request contains a valid Form Post with ...
- ID3097: ServiceHost does not contain any valid Endpoints. Add at least one valid endpoint in the SecurityTokenServiceConfiguration.TrustEndpoints ...
- ID3098: ServiceHost contains an invalid Endpoint. At least one endpoint in the SecurityTokenServiceConfiguration.TrustEndpoints ...
- ID3113: The WSTrustServiceContract does not support receiving '{0}' messages with the '{1}' SOAP action. If you need to support ...
- ID3130: A WSTrust 1.3 RequestSecurityToken SecondaryParameters element cannot contain another SecondaryParameters element. ...
- ID3137: The TrustVersion '{0}', is not supported, only 'TrustVersion.WSTrust13' and 'TrustVersion.WSTrustFeb2005' is supported. ...
- ID3139: The WSTrustChannel cannot compute a proof key. The KeyType '{0}' is not supported. Valid proof key types supported ...
- ID3140: Specify one or more BaseAddresses to enable metadata or set DisableWsdl to true in the SecurityTokenServiceConfiguration. ...
- ID3141: The RequestType '{0}', is not supported. If you need to support this RequestType, override the corresponding virtual ...
- ID3150: Cannot find an output message type for PortType '({0}, {1})' for operation '{2}' in the given ServiceDescription. ...
- ID3151: The WS-Trust message has an empty 'RenewTarget' element. The 'RenewTarget' element must either contain a valid SecurityToken ...
- ID3152: The WS-Trust message has an empty 'OnBehalfOf' element. The 'OnBehalfOf' element must either contain a SecurityToken ...
- ID3153: The WS-Trust message has an empty 'ActAs'. The element must have a SecurityToken or SecurityTokenReference as its ...
- ID3154: The WS-Trust message has an empty 'KeySize' element. The element must specify a valid key size for the requested ...
- ID3155: The WS-Trust message has an empty 'UseKey' element. The element must specify a valid SecurityTokenReference to the ...
- ID3156: The WS-Trust message has an empty 'InformationCardReference'. The element must contain a valid reference to an InformationCard. ...
- ID3158: The WS-Trust message has an empty 'RequestedSecurityToken'. The element must contain a valid SecurityToken as its ...
- ID3159: The WS-Trust message has an empty 'RequestedAttachedReference'. The element must contain a valid SecurityKeyIdentifierClause ...
- ID3160: The WS-Trust message has an empty 'RequestedUnattachedReference'. The element must contain a valid SecurityKeyIdentifierClause ...
- ID3161: The WS-Trust message has an empty 'Lifetime'. The element must contain 'Created' and 'Expires' elements as its child ...
- ID3163: The WS-Trust message has an empty 'RequestedDisplayToken'. The element must contain valid DisplayClaims and DisplayLanguage. ...
- ID3165: The WS-Trust message contains a 'UseKey' element that cannot be read by any of the configured SecurityTokenHandlers. ...
- ID3166: The 'UseKey' token contained in the WS-Trust message is not able to create an RsaKeyIdentifierClause or an X509R ...
- ID3173: The Information Card has an empty 'InformationCardReference' element. The element must contain a 'CardId' and 'CardVersion' ...
- ID3175: The Information Card has an 'InformationCardReference' element that is missing the required 'CardVersion' element. ...
- ID3176: The Information Card has an empty 'TokenServiceList'. The element must have a 'TokenService' as its child element. ...
- ID3177: The Information Card has an 'TokenServiceList/TokenService' element that is missing the required 'UserCredential' ...
- ID3178: The Information Card has an empty 'TokenServiceList/TokenService'. The element must have a 'UserCredential' as its ...
- ID3179: The Information Card has an empty 'SelfIssuedCredentials' element. The element must have a 'PrivatePersonalIdentifier' ...
- ID3180: The Information Card has an 'SelfIssuedCredentials' element that is missing the required 'PrivatePersonalIdentifier' ...
- ID3183: The Information Card has a 'X509V3Credentials/X509IssuerSerial' element that is missing the required 'X509IssuerName'. ...
- ID3184: The Information Card has a 'X509V3Credentials/X509IssuerSerial' element that is missing the required 'X509SerialNumber'. ...
- ID3186: The Information Card has a 'TokenService' element with an 'X509V3Credentials/X509Data' element that does not contain ...
- ID3187: The Information Card has a 'TokenService' element with an 'X509V3Credentials/X509IssuerSerial' that has an empty ...
- ID3188: The Information Card has a 'TokenService' element with an 'X509V3Credentials/X509IssuerSerial' that has an empty ...
- ID3190: The WSTrustChannel cannot compute a proof key without a valid SecurityToken set as the RequestSecurityToken.UseKey ...
- ID3191: The WSTrustChannel received a RequestedSecurityTokenResponse message containing an Entropy without a ComputedKeyAlgorithm. ...
- ID3192: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse does not contain a RequestedProofToken ...
- ID3193: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse indicates that the proof ...
- ID3194: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse indicates that the proof ...
- ID3196: The ChannelFactory provided is not configured to use an FederatedClientCredentials. Ensure that you call the ConfigureChannelFactory ...
- ID3207: An error occurred while reading the metadata document. Attribute '{0}' of element '{1}' has a value '{2}' that is ...
- ID3215: The encoding type '{0}' specified in element '{1}' with namespace '{2}' is not supported. The supported encoding ...
- ID3218: WS-Trust message has an empty 'ProofEncryption'. The element must have a SecurityToken or SecurityTokenReference ...
- ID3219: WS-Trust message has an empty 'DelegateTo'. The element must have a SecurityToken or SecurityTokenReference as its ...
- ID3220: WS-Trust message has an empty 'CancelTarget'. The element must have a SecurityToken or SecurityTokenReference as ...
- ID3221: WS-Trust message has an empty 'ValidateTarget'. The element must have a SecurityToken or SecurityTokenReference as ...
- ID3225: UserNameWSTrustBinding in SecurityMode.Transport SecurityMode, clientCredentialType must be Digest or Basic. But ...
- ID3226: SecurityMode of IssuedTokenBinding must be SecurityMode.Message or SecurityMode.TransportWithMessageCredential. But ...
- ID3227: Issued token authentication is not supported for Transport security. IssuedTokenWSTrustBinding.SecurityMode must ...
- ID3257: RequestSecurityToken contains at least one Claim with a Claim value specified but the RequestClaimCollection.Dialect ...
- ID3258: RequestSecurityToken contains a Claim with a Claim value specified but the Dialect is set to '{0}'. The Dialect must ...
- ID3262: The CardVersion element in the Information Card has a value that is out of range. It must be an integer greater than ...
- ID3263: WS-Trust message has an 'InformationCardReference' element with an invalid CardVersion. The Information Card version ...
- ID3264: OnBehalfOf element was found, but there was no token handlers registered to read a OnBehalfOf element. Consider adding ...
- ID3265: ActAs element was found, but there was no token handlers registered to read a ActAs element. Consider adding a valid ...
- ID3266: The FederatedSecurityTokenProvider cannot support the FederatedClientCredentialsParameters. The FederatedClientCredentialsParameters ...
- ID3269: Cannot determine the TrustVersion. It must either be specified explicitly, or a SecurityBindingElement must be present ...
- ID3270: The WSTrustChannel does not support multi-leg issuance protocols. The RSTR received from the STS must be enclosed ...
- ID3272: Cannot determine the URL of the STS to which to redirect with wsignout1.0. Specify an absolute URL in the 'signOutUrl' ...
- ID3273: The 'wreq' parameter or the data retrieved by the 'wreqptr' parameter must contain valid XML for a WS-Federation ...
- ID3275: The XmlReader is not positioned at an EncryptedData element. XmlReader is positioned at: Name: '{0}', Namespace: ...
- ID4007: The symmetric key inside the requested security token must be encrypted. To fix this, either override the SecurityTokenService.GetScope() ...
- ID4013: Cannot return null from Saml11SecurityTokenHandler.CreateAssertion. To fix this, make sure CreateAssertion returns ...
- ID4022: The key needed to decrypt the encrypted security token could not be resolved. Ensure that the SecurityTokenResolver ...