Certificates are now finally correctly assigned to each key, but pay attention to the command to (re)assign them...
mymac:~ waider$ sudo serveradmin settings notifications:sslKeyFile = "/etc/certificates/mymac.mydomain.com.E9A509E12E8D8CE04165291F2781DC44A85F1832. concat.pem"
mymac:~ waider$ sudo serveradmin settings notifications:sslCAFile = "/etc/certificates/mymac.mydomain.com.E9A509E12E8D8CE04165291F2781DC44A85F1832. chain.pem"
When typing the command "serveradmin settings notification:sslKeyFile" type notification without "s".
It worked for me... for the certificate part. I still get disconnections from apple servers.
The disconnect from the feedback server is not an error, although the null would suggest otherwise. The feedback server needs to be polled intermittently to see if there's any devices that are no longer registered or responding to the profile manager's requests -- in essence, this is the feedback loop from the server (on Apple's side) to let your server know "there's nothing to report."
My turn to have a Notification pb, here is the error that shows in the log :
[twistedcaldav.notify.Notifier#warn] Could not create node /CalDAV/myserver.com/6391362A-D9D8-46B8-9568-4649C42F0824/
2012-08-14 12:38:25+0200 [-] [caldav-3] [-] [twistedcaldav.notify.Notifier#warn] Could not create node /CalDAV/lmyserver.com/6391362A-D9D8-46B8-9568-4649C42F0824/
any idea ...
Hi I had this exact issue with clean install of Lion Server 10.7.5 with no services initiated except the web service was turned on and I had also set valid verified SSL certificate. The same repeating error arose after restarting the server -com.apple.APNBridge: Unable to find identity com.apple.APNBridge.httpscom.apple.APNBridge: Unable to configure SSL. Not starting HTTP Server
jabberd_notification/router: [127.0.0.1, port=49541] connect
jabberd_notification/router: [127.0.0.1, port=49541] disconnect
com.apple.launchd (com.apple.APNBridge): Exited with code: 1
com.apple.launchd (com.apple.APNBridge): Throttling respawn: Will start in 10 seconds
As noted by the gurus in this post (and other key posts thanks Mark 23 Beno44 Drizzt others) the issue is with the SSL Certificate set for APN.
The common cause of this issue is that when you set up OD by pressing the "configure" button in ProM settings (as per numerous authoritative recommendations - 318, ToddOlthoff, Ars Technica to create a stable ProM) which then creates an OD master -
= this creates a new certificate (which you can see by pressing the SSL Certificate "edit" button which has the title "[your domain name].com - [your domain name].com OD Intermediate CA"
Alternatively it is in keychain and although it is headed with [your domain name].com it is issued by "IntermediateCA_[your DOMAIN NAME].COM_1" (note capitals).
ARS TECNICA noted the creation of the 2nd certificate and recommended to configure the OD separately.
The solution is to set the "OD" certificate with the SSL "edit button
Watch the system log (from the Console App (in the Utilities folder)) as it now loads jabber notifications etc.
The extra solution is that you can set the SSL certificate for OD in SAdmin/Settings/LDAP checkbox to "Enable SSL" then select your Verified 3rd Party SSL Certificate from the drop down menu as the SSL for OD
then back at SApp reset your 3rd Party certificate again
watch the system log loading jabber notifications as before
Now that the OD is set with the right SSL the Certificate you set in SApp will match
Hope this helps