text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The configuration-specified type {0} must be public, and is not. No current HttpContext was detected, so an {0} instance must be explicitly provided or specified in the .config file. Call the constructor overload that takes an {0}. The configuration XAML reference to {0} requires a current HttpContext to resolve. The current IHttpHandler is not one of types: {0}. An embedded resource URL provider must be set in your .config file. The empty string is not allowed. The argument has an unexpected value. The property {0} must be set before this operation is allowed. This object contains a response body, which is not supported. The HostFactories property must be set first. The provided data could not be decrypted. If the current application is deployed in a web farm configuration, ensure that the 'decryptionKey' and 'validationKey' attributes are explicitly specified in the <machineKey> configuration section. The requested access scope exceeds the grant scope. The access token's private signing key must be set. The callback URL ({0}) is not allowed for this client. Failure looking up secret for client or token. The client secret was incorrect. Invalid resource owner password credential. No callback URI was available for this request. The PAPE request has an incomplete set of authentication policies. A PAPE response is missing or is missing required policies. No personally identifiable information should be included in authentication responses when the PAPE authentication policy http://www.idmanagement.gov/schema/2009/05/icam/no-pii.pdf is present. No personally identifiable information should be requested when the http://www.idmanagement.gov/schema/2009/05/icam/no-pii.pdf PAPE policy is present. No PPID provider has been configured. Discovery on the Realm URL MUST be performed before sending a positive assertion. The Realm in an authentication request must be an HTTPS URL. The request message type {0} should not be responded to with a refresh token. The Authorization Server's token endpoint generated error {0}: '{1}' Access token has expired and cannot be automatically refreshed. Authorization has expired. Unexpected OAuth authorization response received with callback and client state that does not match an expected value. Failed to obtain access token. Authorization Server reports reason: {0} Unexpected response Content-Type {0} Argument's {0}.{1} property is required but is empty or null. HttpContext.Current is null. There must be an ASP.NET request in process for this operation to succeed. DataContractSerializer could not be initialized on message type {0}. Is it missing a [DataContract] attribute? DataContractSerializer could not be initialized on message type {0} because the DataContractAttribute.Namespace property is not set. An instance of type {0} was expected, but received unexpected derived type {1}. The directed message's Recipient property must not be null. The given set of options is not supported by this web request handler. Error while deserializing message {0}. Error occurred while sending a direct message or getting the response. This exception was not constructed with a root request message that caused it. Expected {0} message but received no recognizable message. The message expired at {0} and it is now {1}. At least one of GET or POST flags must be present. This method requires a current HttpContext. Alternatively, use an overload of this method that allows you to pass in information without an HttpContext. Messages that indicate indirect transport must implement the {0} interface. Insecure web request for '{0}' aborted due to security requirements demanding HTTPS. The {0} message required protections {{{1}}} but the channel could only apply {{{2}}}. The customized binding element ordering is invalid. Some part(s) of the message have invalid values: {0} The incoming message had an invalid or missing nonce. An item with the same key has already been added. The {0} message does not support extensions. The value for {0}.{1} on member {1} was expected to derive from {2} but was {3}. Error while reading message '{0}' parameter '{1}' with value '{2}'. Message parameter '{0}' with value '{1}' failed to base64 decode. Error while preparing message '{0}' parameter '{1}' for sending. A message response is already queued for sending in the response stream. This message has already been processed. This could indicate a replay attack in progress. This channel does not support replay protection. The following required non-empty parameters were empty in the {0} message: {1} The following required parameters were missing from the {0} message: {1} The binding element offering the {0} protection requires other protection that is not provided. The list is empty. The list contains a null element. Message signature was incorrect. This channel does not support signing messages. To support signing messages, a derived Channel type must override the Sign and IsSignatureValid methods. The stream's CanRead property returned false. The stream's CanWrite property returned false. Expected at most 1 binding element to apply the {0} protection, but more than one applied. The maximum allowable number of redirects were exceeded while requesting '{0}'. The array must not be empty. The empty string is not allowed. Message parameter '{0}' had unexpected value '{1}'. Expected message {0} parameter '{1}' to have value '{2}' but had '{3}' instead. Expected message {0} but received {1} instead. Unexpected message type received. A null key was included and is not allowed. A null or empty key was included and is not allowed. A null value was included for key '{0}' and is not allowed. The type {0} or a derived type was expected, but {1} was given. {0} property has unrecognized value {1}. The URL '{0}' is rated unsafe and cannot be requested this way. Redirects on POST requests that are to untrusted servers is not supported. Web request to '{0}' failed. This exception must be instantiated with a recipient that will receive the error message, or a direct request message instance that this exception will respond to. '{0}' messages cannot be received with HTTP verb '{1}'. Unexpected HTTP status code {0} {1} received in direct response. The HTTP verb '{0}' is unrecognized and unsupported. A non-empty string was expected. The stream must have a known length. Unable to send all message data because some of it requires multi-part POST, but IMessageWithBinaryData.SendAsMultipart was false. An HttpContext.Current.Session object is required. This message factory does not support message type(s): {0} The following message parts had constant value requirements that were unsatisfied: {0} Unable to instantiate the message part encoder/decoder type {0}. This message has a timestamp of {0}, which is beyond the allowable clock skew for in the future. This blob is not a recognized encryption format. Failed to add extra parameter '{0}' with value '{1}'. The message part {0} was expected in the {1} message but was not found. Message too large for a HTTP GET, and HTTP POST is not allowed for this message type. Missing decryption key for bucket "{0}" handle "{1}" Unexpected buffer length. Decoding failed due to data corruption. Cannot send access token to Consumer for request token '{0}' before it has been authorized. The access token '{0}' is invalid or expired. Failure looking up secret for consumer or token. oauth_verifier argument was incorrect. An invalid OAuth message received and discarded. The {0} message included extra data which is not allowed. This OAuth service provider requires OAuth consumers to implement OAuth {0}, but this consumer appears to only support {1}. Cannot send OAuth message as multipart POST without an authorization HTTP header because sensitive data would not be signed. Use of the OpenID+OAuth extension requires that the token manager in use implement the {0} interface. The OpenID Relying Party's realm is not recognized as belonging to the OAuth Consumer identified by the consumer key given. The request URL query MUST NOT contain any OAuth Protocol Parameters. The signing element already has been associated with a channel. All signing elements must offer the same message protection. A token in the message was not recognized by the service provider. The RSA-SHA1 signing binding element has not been set with a certificate for signing. An absolute URI is required for this value. The access token contains characters that must not appear in the HTTP Authorization header. At least one parameter is required for the Bearer scheme in its WWW-Authenticate header. This message can only be sent over HTTPS. The scope token "{0}" contains illegal characters or is empty. Refresh tokens should not be granted without the request including an access grant. The '{0}' parameter contains the illegal character '{1}'. The return value of {0}.{1} should never be null. Individual scopes may not contain spaces. The length of the shared secret ({0}) does not match the length required by the association type ('{1}'). The length of the encrypted shared secret ({0}) does not match the length of the hashing algorithm ({1}). If an association store is given, a nonce store must also be provided. The private data supplied does not meet the requirements of any known Association type. Its length may be too short, or it may have been corrupted. Callback arguments are only supported when a {0} is provided to the {1}. A Simple Registration request can only generate a response on the receiving end. The openid.claimed_id and openid.identity parameters must both be present or both be absent. The ClaimedIdentifier property cannot be set when IsDelegatedIdentifier is true to avoid breaking OpenID URL delegation. The ClaimedIdentifier property must be set first. The following properties must be set before the Diffie-Hellman algorithm can generate a public key: {0} URI is not SSL yet requireSslDiscovery is set to true. An extension sharing namespace '{0}' has already been added. Only one extension per namespace is allowed in a given request. Cannot lookup extension support on a rehydrated ServiceEndpoint. Fragment segments do not apply to XRI identifiers. ClaimedIdentifier and LocalIdentifier must be the same when IsIdentifierSelect is true. {0} (Contact: {1}, Reference: {2}) Cannot encode '{0}' because it contains an illegal character for Key-Value Form encoding. (line {1}: '{2}') Cannot decode Key-Value Form because a line was found without a '{0}' character. (line {1}: '{2}') The scheme must be http or https but was '{0}'. The value '{0}' is not a valid URI. Not a recognized XRI format. The OpenID Provider issued an assertion for an Identifier whose discovery information did not match. Assertion endpoint info: {0} Discovered endpoint info: {1} The list of keys do not match the provided dictionary. The '{0}' and '{1}' parameters must both be or not be '{2}'. No recognized association type matches the requested length of {0}. No recognized association type matches the requested name of '{0}'. Unless using transport layer encryption, "no-encryption" MUST NOT be used. Diffie-Hellman session type '{0}' not found for OpenID {1}. No OpenID endpoint found. This operation is only allowed when IAuthenticationResponse.State == AuthenticationStatus.SetupRequired. Unable to determine the version of the OpenID protocol implemented by the Provider at endpoint '{0}'. An HTTP request to the realm URL ({0}) resulted in a redirect, which is not allowed during relying party discovery. return_to '{0}' not under realm '{1}'. The {0} parameter ({1}) does not match the actual URL ({2}) the request was made with. The openid.return_to parameter is required in the request message in order to construct a response, but that parameter was missing. The following parameter(s) are not included in the signature but must be: {0} Invalid birthdate value. Must be in the form yyyy-MM-dd. The type must implement {0}. Unsolicited assertions are not allowed from 1.0 OpenID Providers. The openid.user_setup_url parameter is required when sending negative assertion messages in response to immediate mode requests. XRI resolution failed. An attribute with type URI '{0}' has already been added. Only {0} values for attribute '{1}' were requested, but {2} were supplied. Providing a DateTime whose Kind is Unspecified is not allowed. The requested association type '{0}' with session type '{1}' is unrecognized or not supported by this Provider due to security requirements. The Provider requested association type '{0}' and session type '{1}', which are not compatible with each other. An authentication request has already been created using CreateRequest(). No OpenID url is provided. An extension with this property name ('{0}') has already been registered. The extension '{0}' has already been registered. This operation is not supported by serialized authentication responses. Try this operation from the LoggedIn event handler. No XRDS document containing OpenID relying party endpoint information could be found at {0}. An unsolicited assertion cannot be sent for the claimed identifier {0} because this is not an authorized Provider for that identifier. The maximum time allowed to complete authentication has been exceeded. Please try again. Unable to find the signing secret by the handle '{0}'. The response is not ready. Use IsResponseReady to check whether a response is ready first. This feature is unavailable due to an unrecognized channel configuration. The openid.identity and openid.claimed_id parameters must either be both present or both absent from the message. The ReturnTo property must not be null to support this operation. Rejecting unsolicited assertions requires a nonce store and an association store. Unsolicited assertions are not allowed at this relying party. Only OpenIDs issued directly by their OpenID Provider are allowed here. XRI support has been disabled at this site. No association store has been given but is required for the current configuration. The property {0} had unexpected value {1}. No identifier has been set. This property value is not supported by this control. This is already a PPID Identifier. Sorry. This site only accepts OpenIDs that are HTTPS-secured, but {0} is not a secure Identifier. The {0} extension failed to deserialize and will be skipped. {1} An positive OpenID assertion was received from OP endpoint {0} and was rejected based on this site's security settings. The HTML head tag must include runat="server". The {0} property must be set first. The X.509 certificate used to sign this document is not trusted. This OpenID exploits features that this relying party cannot reliably verify. Please try logging in with a human-readable OpenID or from a different OpenID Provider. Missing {0} element. The associate request instance must be a Diffie-Hellman instance. Invalid XmlDSig signature on XRDS document. X.509 signing certificate issued to {0}, but a certificate for {1} was expected. OpenID popup window or iframe did not recognize an OpenID response in the request. Unrecognized or missing canonicalization method. Unrecognized or missing signature method. Client Identifier starts with a resource owner prefix. Authorization aborted. Invalid access token. Missing access token. Resource owner username starts with a client prefix. Authorization aborted. Web application '{0}' deleted. The {0} and {1} properties must be set to arrays of equal length. No web site with the name '{0}' found. Packing javascript resource "{0}" into "{1}". Skip packing "{0}" because its packed version is up to date. Web application '{0}' was not found, so it was not deleted. XRI CanonicalID verification failed. Failure parsing XRDS document. The XRDS document for XRI {0} is missing the required CanonicalID element. Could not find XRI resolution Status tag or code attribute was invalid.