My application sends notification the .p12 certificate expiring soon so do we need to send the application again to Apple store ?
If not then we just create wlapp file with new .p12 certificate and deploy on our Mobilefirst server or we need to do more configuration ?
Please advice ?
My application sends notification the .p12 certificate expiring soon so do we need to send the application again to Apple store ?
No.
If not then we just create wlapp file with new .p12 certificate and deploy on our Mobilefirst server?
You could replace the certificate in the project and re-build it so an updated .wlapp file is created, and then deploy this .wlapp file to the MobileFirst Server.
Alternatively, instead of rebuilding the application, you call also call a server endpoint to update only the certificate. See here: http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.apiref.doc/apiref/r_restapi_apns_credentials_put.html
Related
We are using Mobilefirst 7.1 for hybrid application. We have implemented certificate pinning in the application. The certificate got expired and we replaced it with the new one. But the application is taking old certificate from Application cache and it is blocking the application to connect to server. After we remove the app cache and app data the application is working fine. Kindly suggest any solution for this?
Can you check if you have kept the same public key as before. Otherwise you will have to release a new version with the renewed certificate. Check this link for further details
I have two client certificates that I have installed for my API project in the Azure portal. I have set the config option to enable them and can verify that they can both be found in the CurrentUser 'My' store. My problem is now that one of them is failing validation. On my local machine I have this cert installed in the Trusted People store of LocalMachine. Is there anything I can with Azure to make this work?
Is the location of the cert the issue or is it possibly something with the certificate itself?
**Note that this is an app service, not a cloud service
There are few things you can check, In Azure check in the app settings whether you have added your certificate. Its in the SSL section of you Azure app.
Another workaround would be where you are configuring your Token Authentication, you could set this settings.
For e.g. In my case, I was getting X509 Certificate error.
I added this code in my project.
System.IdentityModel.Configuration.IdentityConfiguration config = new System.IdentityModel.Configuration.IdentityConfiguration();
config.CertificateValidator = X509CertificateValidator.None;
config.CertificateValidationMode = X509CertificateValidationMode.None;
Basically turn off your validation. Most of the times, what happens is your local machine as all the certificates installed by an IT Operation person, but Those certificates are not on Azure.
You can check here for some reference as well. Microsoft Certificate Reference
Why do I get this message by Production APNS certificate?
"The certificate environment did not match. Ensure that you got the right development or production APNS certificate."
What is exactly 'The certificate environment'?
Development APNS certificate makes no problem.
I don't get it.
I had the same issue and here's what I did to solve.
The issue was because I generate both Development APNS Certificate and Production APNS Certificate using the same certificate signing request file (the file that you got from Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority). Apparently, the certificate signing request file should not be the same.
To solve this problem:
Create a new certificate signing request (Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority)
From the Push Notification section of your app, Create Certificate using the .certSigningRequest file you just created
Re-upload the .p12 to GCM
Reference:
http://blog.hypermkt.jp/uploading-certificate-for-google-cloud-messaging-for-ios/
How to generate valid APNS Certificate (.p12) for use in GCM for iOS?
Had the same issue!
While exporting from Keychain right click on Certificate itself not on the Private Key inside of it.
We have a HTTPS RESTFul service running in IIS. We are able to successfully call it using the browser. However, when we call the service from a worklight adapter, we are getting the following exception:
"javax.net.ssl.SSLPeerUnverifiedException"
The worklight adapter was working perfectly fine when we were using HTTP instead of HTTPS.
We have followed all the steps mentioned in the documentation:
Create certificate using keytool in the IIS server. Bind it to the RestFul service.
Exporting the public key to a .cert file
Importing the file into Worklight keystore
Mentioned https as the protocol in the adapter.xml.
We have even verified the default.keystore of the worklight, it is matching with the certificate present in the IIS server.
We don't need mutual authentication. We just want to use SSL in the RestFul service deployed in the IIS.
Thanks,
Pavan
You forgot to add the certificate to your device's trust store. Since it is self signed, devices will not trust them by default. To do so, follow the steps here for your device's OS: http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/c_ssl_config.html?lang=en
Specifically, look at this for iOS and this one for Android.
I am hosting asp.net mvc 4 app in azure web site.
Where can I store the apple/windows push notification p12 cert?
Should I create a folder, and how can I retrieve it?
Include the cert as content then load it before initializing the APN. You can "load" it with X509Certificate2 and X509CertificateCollection2 and use it with SslStream.AuthenticateAsClient For an example, see http://simonguest.com/2011/04/21/using-apple-push-notifications-from-windows-azure/