text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 An attribute with type URI '{0}' has already been added. Only {0} values for attribute '{1}' were requested, but {2} were supplied. 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. The ClaimedIdentifier property must be set first. An authentication request has already been created using CreateRequest(). HttpContext.Current is null. There must be an ASP.NET request in process for this operation to succeed. An encrypted session using either HTTPS or Diffie-Hellman is required when establishing associations between relying parties and providers. OpenID parameter '{0}' was expected to be base64 encoded but is not. The nonce has expired. It was good until {0} (UTC), and it is now {1} (UTC). If this looks wrong, check the server's clock, time zone and daylight savings settings. An extension sharing namespace '{0}' has already been added. Only one extension per namespace is allowed in a given request. Extension parameter key '{0}' encountered, but extension parameter keys should not include their prefix. The OpenID parameter '{0}' must be signed by the OpenID Provider, but was not. Fragment segments do not apply to XRI identifiers. No current ASP.NET HttpContext was detected. Use an overload that does not require one. No current HttpContext was detected, so an IAssociationStore must be explicitly provided. Call the Server constructor overload that takes an IAssociationStore. This operation is only allowed when IsIdentifierSelect is true. ClaimedIdentifier and LocalIdentifier must be the same when IsIdentifierSelect is true. Inconsistent setting of application state. Authentication request was sent with application state available, but authentication response was received without it available. This makes it impossible to validate the token's signature and will cause assertion verification failure. 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 nonce was not in the expected format. OpenID extension {0} parameter {1} had unexpected value '{2}'. OpenID parameter '{0}' had unexpected value '{1}'. OpenID parameter '{0}' with value '{1}' failed to base64 decode. The scheme must be http or https but was '{0}'. The signature verification failed. The value '{0}' is not a valid URI. Failure parsing XRDS document. Not a recognized XRI format: '{0}'. The OpenId Provider issued an assertion for an Identifier whose discovery information did not match. The given key '{0}' already exists. The list of keys do not match the provided dictionary. The '{0}' and '{1}' parameters must both be or not be '{2}'. The XRDS document for XRI {0} is missing the required CanonicalID element. Query parameter '{0}' was missing from the query. OpenID parameter '{0}' was missing from the query. Query parameter '{0}' was expected in the return_to query '{1}'. No XRDS document containing OpenId relying party endpoint information could be found at {0}. No OpenId endpoint found. No OpenId url is provided. Prefix should not begin or end with a period. Unable to determine provider's OpenID version. The OpenId Provider responded with an error: '{0}'. The OpenId Provider responded with unrecognized HTTP status code {0}. An HTTP request to the realm URL ({0}) resulted in a redirect, which is not allowed during relying party discovery. The nonce has already been used. OpenId provider's response is not ready. Use IsResponseReady to check, and fill in the required properties first. The '{0}' parameter does not have the same value for return_to ('{1}') and the regular query ('{2}'). return_to '{0}' not under realm '{1}'. The {0} parameter does not match the actual URL the request was made with. The '{0}' parameter was expected to have the value '{1}' but had '{2}' instead. The type must implement {0}. The URL '{0}' is rated unsafe and cannot be requested this way. Providing a DateTime whose Kind is Unspecified is not allowed.