Bug 24901 - System.Net.FtpWebRequest.ClientCertificates throws error "The requested feature is not implemented"
Summary: System.Net.FtpWebRequest.ClientCertificates throws error "The requested featu...
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-11-27 15:01 UTC by Anubhav Ranjan
Modified: 2014-11-30 08:01 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Anubhav Ranjan 2014-11-27 15:01:00 UTC
One of the client is trying to make use of 
System.Net.FtpWebRequest.ClientCertificates but gets this error 
"The requested feature is not implemented"

##Although, looking at the code seems like it's not implemented in Mono.
https://github.com/mono/mono/blob/master/mcs/class/System/System.Net/FtpWebRequest.cs#L109


##Code Used: 

private void Connection_FTP(string sfile_certificate)
{
    ServicePointManager.ServerCertificateValidationCallback
        = new RemoteCertificateValidationCallback(myCertificateValidation);
    FtpWebRequest request =
        (FtpWebRequest)WebRequest.Create("ftp://xxxxxx.com");

    request.Method = WebRequestMethods.Ftp.ListDirectory;
    request.EnableSsl = true;
    request.Credentials = new NetworkCredential("xxxxxx", "xxxxxx");
    
    char[] cPw = new char[]{'s','i','a','C','l','i','e','n','t','C','e','r','t'};
    SecureString pwCert = new SecureString();

    int j = 0;
    while(j < cPw.Length)
        pwCert.AppendChar(cPw[j++]);

    request.ClientCertificates.Add(new X509Certificate(sfile_certificate pwCert));

    WebResponse response = null;

    try
    {
        response = request.GetResponse();
    }
    catch(Exception respEx)
    {

    }
}

public bool myCertificateValidation(Object sender,
    X509Certificate cert, X509Chain chain, SslPolicyErrors Errors)
{
    return (true);
}

Note You need to log in before you can comment on or make changes to this bug.