Previously we were using Baikal ver. 0.5.3, which we tested for Thunderbird and Mac OSX Calendar, recently we upgraded to ver. 0.6.0, after that Thunderbird is working but Mac OSX Calendar is not working,
error logs :
user not authorized: Baikal DAV: No 'Authorization: Basic' header found. Either the client didn't send one,
or the server is misconfigured. Login was needed for privilege: {DAV:}read on principals/xyz#rediff-inc.com
I am using this URL for MacOSX : http://domainz.com/cal.php/principals/xyz#domainz.com
Newer MacOSX doesn't send credentials in Auth header in plain text http request, after enabling TLS on server i.e https, everything worked fine.
Related
I am having trouble using Guzzle within a local environment via MAMP.
The site is using SSL.
The error is as seen below:
Uncaught GuzzleHttp\Exception\RequestException: cURL error 77: error setting certificate verify locations: CAfile: /Applications/MAMP/Library/OpenSSL/cert.pem CApath: none (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
I was developing on a Windows machine using XAMPP, and things were working without issue. I was not developing using SSL at that time. I have migrated to a Mac and since have began using MAMP.
Things works as expected when deployed to a true staging server that also uses SSL.
we have set up a CalDAV server here with SOGo as backend and frontend (WEBUI). Which is working as expected.
But there are some errors which I cannot reproduce and the logging also gives no hint since there is no logging:
1) macOS 10.11 - latest release
I can login to CalDAV, I can create entries (which are synced) and they show up in WEBUI. But events created in WEBUI are not synced.
2) Same credentials, same usage on iPhone iOS12 - I can't even log in to the calender.
Here the HTTP error in the log indicates a "Forbidden"...but as stated the credentials are correct - maybe iOS sends a authentication methode which is not installed on my server?
Dan
The answer to this question is very simple and seems intuitive:
Install SSL certificate for https connections to SOGo web-root
Forward all http requests to https
I have a Facebook app which is defined in Facebook as localhost.
I have it installed on a windows server 2012 with a self signed certificate issues to that server name.
In the IE (and chrome), if I open https://localhost it doesn't go through the Facebook and fails on certificate, if I open https://servername it goes through the Facebook but again, doesn't open claiming it doesn't have a valid security certificate.
I created 2 certificates, one for localhost (issues by "localhost") and one for the servername, both don't work.
I tried everything I could find online and some advice from friends including changing security settings on IE.
Any ideas will be appreciated
Thank you
(According to https://developers.facebook.com/tools-and-support/ there are Facebook engineers reading this.)
Some of our web hosting customers recently complained about missing images/text when sharing content from their https website to Facebook.
I tracked this problem to a security change in our environment that disabled TLS v1.0 for customer HTTPS sites. The curl output in Facebook Debugger merely showed an SSL connection error and I can reproduce the problem locally if I force curl to not try TLS v1.1 nor v1.2.
These values in Apache 2.4 vhost configuration makes Facebook not connect to my customers site:
SSLProtocol All -SSLv2 -SSLv3 -TLSv1
Changing SSLProtocol to this make Facebook work OK:
SSLProtocol All -SSLv2 -SSLv3
'All' includes TLS v1.1 and v1.2. Why doesn't Facebook link-sharing and the Facebook Debugger work against modern sites that use TLS v1.1 and TLS v1.2 (and have SSLv3 & TLSv1 disabled)?
Thanks.
I am developing an iPhone application that deals with Facebook. I am using the latest SDK facebook-facebook-ios-sdk-cf1c2c3 (SDK 2.0) to allow the user to login to Facebook account using OAuth.
User can login without any problem in device iPod Touch(4.3.1). But in iPhone 3GS I get the following error:
Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be \u201cm.facebook.com\u201d which could put your confidential information at risk." UserInfo=0x1b8350 {NSErrorFailingURLStringKey=https://m.facebook.com/dialog/oauth?type=user_agent&display=touch&redirect_uri=fbconnect://success&sdk=2&scope=read_stream,publish_stream&client_id=<APP_ID>, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, NSErrorFailingURLKey=https://m.facebook.com/dialog/oauth?type=user_agent&display=touch&redirect_uri=fbconnect://success&sdk=2&scope=read_stream,publish_stream&client_id=<APP_ID>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be \u201cm.facebook.com\u201d which could put your confidential information at risk., NSUnderlyingError=0x1b83a0 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be \u201cm.facebook.com\u201d which could put your confidential information at risk.", NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x1be310>}
I extracted the URL from the FBLoginDailog and tried loading it in iPhone -> Safari. It redirects to the following URL and allows the user to login:
http://m.facebook.com/login.php?app_id=<APP_ID>&sdk=2&cancel=fbconnect://success?error_reason=user_denied&error=access_denied&error_description=The+user+denied+your+request.&fbconnect=1&next=https://www.facebook.com/connect/uiserver.php?method=permissions.request&app_id=<APP_ID>&display=touch&redirect_uri=fbconnect;//success&sdk=2&type=user_agent&fbconnect=1&perms=read_stream,publish_stream&from_login=1&rcount=1
Also, I have find the following workaround from the link:
https://github.com/facebook/facebook-ios-sdk/issues/139
But, the link also mentions not to use it for App Store executable. But, I am getting the problem for app store executable also.
How do I solve this?
This was not SDK problem. The date and time set in Device (3GS) was improper.