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/
Related
I have an Azure Function calling an HTTPS endpoint using an SSL certificate that was provided by an internal Root CA.
Without doing anything, I have an SSL negotiation error which is normal.
I added the ROOT CA cert in the SSL Settings of my Function App, and I also added the setting WEBSITE_LOAD_ROOT_CERTIFICATES in the Function App Settings.
By using the Kudu Console, I tried to curl my HTTPS endpoint, and I'm still having SSL troubles.
Am I missing something?
You can't use an internal authority signed certificate against an Azure Function that is in a multi-tenant environment. The only available approach is to use App Service Environment (ASE). Using ASE, will enable you to upload an issuing and root certificates that are signed by a private/internal authority and register them in the store to be able to be interrogated.
Try to follow the below steps to enable SSL.
Go to App service and then select TLS/SSL settings.
Click on Private Key Certificates and then click on Create App Service Managed Certificate. It opens a side window in that window click on create button.
After successfully created, go to custom domains and click on Add binding.
Under TLS/SSL binding, select custom domain name, private certificate thumbprint, and its type then click on Add Binding.
Once we finished the above steps then it will add to your domain.
As per the Microsoft Document, Add a TLS/SSL certificate in Azure App Service.
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
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
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 would ideally want it to work on my the server on my laptop, as well as the website I deploy to. The reason being so I can send push notifications to the iOS app.
The certificate depends on the web server, correct? So what kind of webserver is meteor?