We are facing a SSL certificate issue while executing Token create Interface from SAP side.
For that while troubleshooting we got new 3 SSL certificates from SAP chain verifier, for this please find attached screenshot.
We downloaded those certificates and found out that the Root certificate is not trusted, also the intermediate certificate is different as per chain verifier. We are attaching all certificates in the zip file, please check.
If possible can you please provide a valid SSL certificate for Google token create API. So we can resolve this issue.
I am trying to add a custom domain with SSL in my google app engine project, according to the steps defined here using-custom-domains-and-ssl, i successfully added my domain but when i am trying to add the cert by going to SSL Certificates tap i am seeing a certificate which is already added, now can anyon eplease tell me, can i use this SSL certificate or will i have to add the cert manually by myself.
That would depend on several factors. You should verify the information in the existing certificate is correct before attempting to use it.
If this was a certificate you added previously AND it matches your domain name AND it is not expired, then yes you can continue to use it.
If any of the above is false, you should import your new certificate instead.
In CEF (Chromium Embedded Framework) support to display Client Certificate list dialog is not available, due to which I cannot display a certificate list using CefSharp browser while using PKI authentication. What CEF does support, is signing the user in by making use of the "first" certificate in the list. This works great if you only have a single certificate on your client.
The problem occurs when you have multiple valid certificates and the only certificate CEF uses is the first one. So is there a workaround for this?
Is there a way to "re-order" the client certificate list, to switch the certificate you need as the first one?
I have a Silverlight 4 trusted OOB app that was signed with a certificate that expired last week. I was unable to release new code on the old certificate.
I applied for a new 5-year certificate and re-signed the app after choosing this new certificate from my certificate store (same Publisher name, company etc.)
Now the auto-updating Silverlight mechanism fails when it tries to update the OOB app to the new version with a Certificate Mismatch error. It obviously does not like the new certificate.
How can I get around this - I would think this is up to the Certificate issuer to "link" my certificates to continue the trust. I don't want to have to get my users to uninstall the software every time my certificate expires and I have to get a new one.
I need to invoke a REST-based service from Windows Phone 7.
The service only accepts the request if the following conditions are satisfied:
The request must happen over HTTPS/SSL
The request must be authenticated with a client X509 certificate
I don't control the service, so I can't change the authentication requirements.
On the full framework, we can do things like this:
HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(uri);
request.ClientCertificates.Add(accessCertificate);
However, the ClientCertificates property isn't available in Silverlight 4, and neither do any of the X509 classes from the System.Security.Cryptography.X509Certificates namespace seem to be available.
Is it really impossible to make Client Certificate-based HTTPS requests from Windows Phone 7?
Client certificates are not supported by the 3rd party WP7 SDK currently.
Confirmation here for your reference.
Problems with client certification authentication on WP7
Whilst it's possible to install certs on the device through email (referenced in an exhcange integration solution), your app won't use them.
There are only 2 ways to install 3rd party certificates on the device and neither can currently be done through code:
Installing certificates via Windows®
Internet Explorer®
A certificate can
be posted on a website and made
available to users through a
device-accessible URL that they can
use to download the certificate. When
a user accesses the page and taps the
certificate, it opens on the device.
The user can inspect the certificate,
and if they choose to continue the
certificate is installed on the
device.
Installing certificates via email
The certificate installer on
Windows Phone 7 supports .cer, .p7b,
and .pfx files. When installing
certificates via email, make sure your
mail filters do not block .cer files.
Certificates that are sent via email
appear as message attachments. When a
certificate is received, a user can
tap to review the contents and then
tap to install the certificate.
Typically, when an identity
certificate is installed the user is
prompted for the passphrase that
protects it.
You'll have to get the user to perform one of these actions before the app will work with the certificate.
From Windows Phone 7 and Certificates_FINAL_121610.pdf
So you can us oAuth for authentication and pass the token in the request header. If you check out acs.codeplex.com you can see how this is done using the Azure ACS system. I realize you may not be using Azure, but the reference app may help. I would also search for oAuth and Windows Phone 7, I have found a few examples that way too.
As far as SSL, you should be able to do that through the browser with out any issue. You can also open any https Url using an HttpWebRequest, etc.