Re: error passing byte[] or strings of encrypted data to Web Service

From: Yunus Emre ALPÖZEN [MCSD.NET] (yemre_at_msakademik.net)
Date: 05/30/05

  • Next message: ChuckD_Duncan: "Re: error passing byte[] or strings of encrypted data to Web Ser"
    Date: Mon, 30 May 2005 20:59:18 +0300
    
    

    U are right. Converting Base64 should fix it. To overcome this issue, I
    prefer to implement a class and mark it serializable and embed my data in
    it. Conversion is done automatically. I used this method for secure file
    transfer over SSL in web services. It works perfectly...

    -- 
    Thanks,
    Yunus Emre ALPÖZEN
    BSc, MCSD.NET
    "Dominick Baier [DevelopMentor]" <dbaier@pleasepleasenospamdevelop.com> 
    wrote in message news:421237632530493895783323@news.microsoft.com...
    > Hello ChuckD_Duncan,
    >
    > try converting your encrypted strings to Base64 prior to sending
    >
    > string s = Convert.ToBase64(byte[])
    >
    > this should be done automatically upon serialization by the proxy 
    > infrastructure (what datatype ends up in your wsdl document) ??
    >
    > ---------------------------------------
    > Dominick Baier - DevelopMentor
    > http://www.leastprivilege.com
    >
    >> passing something simple like:
    >> bool result = Sample("first", "second");
    >> works fine... but when the two args are replaced by encrypted strings,
    >> I
    >> get the same "object not set to an instance" error message as in the
    >> start of this thread.
    >>
    >> bool result = Sample( szEncryp, szXMLPublicKey);
    >>
    >> also blows up if the first parm is NOT encrypted at all, just "xyz".
    >> The
    >> XML string is in fact a well-formed XML:
    >> string szXMLPublicString = provider_alg.GetXMLString(false); //
    >> and
    >> can be viewed and verified as a valid XML string.
    >> Help??
    >>
    >
    >
    > 
    

  • Next message: ChuckD_Duncan: "Re: error passing byte[] or strings of encrypted data to Web Ser"

    Relevant Pages

    • Re: Current JSON Proposal in ES4
      ... String.parseJSON <-- should return what, ... Object should not always have data structure functionality. ... also supports a specialized serialization. ... in the face of a growing use of JSON as a data exchange ...
      (comp.lang.javascript)
    • Re: XmlSerializer Collection with Collections
      ... What you can do here is hide the OptionList from serialization as follows: ... > public class TestSerializer ... > public int AddQuestion(Question question) ... > public Question(string QuestionText, string Type, int Score, bool ...
      (microsoft.public.dotnet.xml)
    • Re: Serializing/Deserializing to Database
      ... into string, such as base64 convertion). ... private void btnDeserialize_Click ... MySavableClass msc = obj as MySavableClass; ... serialization for further reference: ...
      (microsoft.public.dotnet.framework)
    • Re: Compiler executable file c:..v1.1.4322csc.exe cannot be found.
      ... most likely you are using default serialization code and impersonation. ... But as the compiler _IS_ there, I don't see why it does this ... options, String compilerDirectory, String compilerExe, String ... CompilerParameters parameters, Evidence evidence) +478 ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Using Classes as List Items
      ... | serialization has three items for that property, ... | Private _Part1 As String ... | Public Property Part1() As String ...
      (microsoft.public.dotnet.languages.vb)