Comment by pjr
Any news on this? I've had similar problem since two updates ago. Not sure if it was because of jolla update or update of our front end server. After that I've had the same "Credentials check FAILED!...
View ArticleComment by mm7540
On the tablet: After uninstalling the plugin, deleting the old config and log file, and re installing, is now working and syncing again.
View ArticleComment by chris.adams
@mm7540 I do expect there to be different bugs in the Tablet's (new) activesync plugin, compared to the Phone's (old) activesync plugin. At the moment we don't have the resources to follow up on many...
View ArticleComment by Nirkus
@daywalker - thank you for the pointer! @chris.adams: does [this](https://together.jolla.com/question/109512/cant-add-microsoft-exchange-account-since-11928-update/?comment=110946#comment-110946) still...
View ArticleComment by daywalker
https://together.jolla.com/question/109512/cant-add-microsoft-exchange-account-since-11928-update/?comment=110946#comment-110946
View ArticleComment by Nirkus
Well, I think we need to debug this - finding the actual issue by testing different server configurations will take forever. I updates my "answer" with some details on those two Exchange services....
View ArticleComment by mm7540
have apparently the same problem, using the 'new' plugin on the tablet (the old plugin on the phone continue to sync on the same server , but I was not brave enough to try to delete and re create the...
View ArticleComment by chris.adams
My understanding is that this error will be hit if the server only supports SSLv3 (and not later TLS protocols) OR if the exchange server is running on Windows Server 2003 (which doesn't handle more...
View ArticleAnswer by Nirkus for Can't add Microsoft Exchange account since 1.1.9.28 update
Hey, have the same error #5 with a specific Exchange server on my Jolla phone. :-/ Sailfish OS 2.0.1.7 Trying to add the Exchange account using devel-su -p jolla-settings: [..] [D]...
View ArticleAnswer by Jonas for Can't add Microsoft Exchange account since 1.1.9.28 update
I also have the same problem on my Jolla Tablet. My "old" account still works on the ph one, but with same settings on the tablet nothing happens.
View ArticleComment by tigeli
@TheGrave Actually there can be two issues.. The SSLv3 one and the other one which is not so known which is the hard limit of Windows 2003 server looking only the first 64 ciphers announced by the...
View ArticleComment by TheGrave
Same stupidity in my company - TLSv1.0 only. Something interesting I spotted in the journalctf logs though: Feb 25 12:02:12 Jolla estart[1678]: [D] saveSettings:110 - [jsa-eas] Saving account settings...
View ArticleComment by daywalker
Our server supports TLS 1.0 and it doesn't work. However i just talked back to my colleagues and good news :D They are in the process of migrating our Exchange Server so TLS 1.2 will be supported in...
View ArticleComment by chris.adams
@nelbrog: the Jolla Tablet uses a new (rewritten) Exchange Active Sync stack. If you have issues with exchange on tablet, please provide any information you can (including logs etc) to me, via email if...
View ArticleComment by tigeli
@SlOrbA The correct fix would be allowing the secure protocols to be used on the Exchange servers. @rudi10 Only SSLv3 is not allowed anymore by default with 1.1.9, the TLSv1 and better should still...
View ArticleComment by nelbrog
I also face the problem that I can't create my exchange account on the jolla tablet, whereas the previously created exchange account on my jolla phone on 1.1.9.28 works flawless. I tested the exchange...
View ArticleComment by SlOrbA
So is there a workaround, until the possible "allow unsecure SSL version" configuration UI option is added or the offending exchange servers IIS is updated from it's out-dated defaults?
View ArticleAnswer by rudi10 for Can't add Microsoft Exchange account since 1.1.9.28 update
This is an issue with unsecure Exchange Server. You can check your server by trying `openssl s_client -connect my-exchange.here.com:443`. Try with options -ssl3, tls1, -tls1_1 and tls1_2. If only ssl3...
View ArticleComment by juho
Thanks for the info Hal! I also had to revert to 1.1.7.28 from 1.1.9. I was wondering if Saimaa would have the fix, but apparently not. Exchange is essential for me too, so I'll just have to wait.
View ArticleComment by Hal
Latest "Saimaa" installed. Still..active sync won't work. Went back to 1.1.7.28 version where all was fine and still waiting if something new comes in future in this issue. I have to have this program...
View ArticleComment by chris.adams
Further investigation showed a couple of issues - one related to SSLv3, but the other related to the cipher version which are supported by the base OS. In some cases (e.g., Windows Server 2003) there...
View ArticleComment by SlOrbA
@chris.adams Thanks for your effort and after reading the rfc7568 I'll actually start using my company Exchange only after TLSv1.1 or newer is available.
View ArticleComment by chris.adams
@late88 @shertell I understand completely, and thanks for your patience up to this point. I hope that in the future we're able to improve our level of protocol and server support to include legacy...
View ArticleComment by shertell
Unfortunately I have to change to another device too. Calendar is that important in daily life nowadays. This is a big dissapointment.
View ArticleComment by late88
I'm afraid I have to change back to android only because of this bug. It's a must have feature for me to cope with my work. Really sad :(
View ArticleComment by SlOrbA
I've been able to duplicate the effect with cURL, but with cURL I'm also able to override defaults with flags. I don't know if cURL project is using the same libraries and how Exchange client calls the...
View ArticleComment by chris.adams
I know very little about that so I cannot comment. We are looking into the possibility of providing an option in the account page to "Allow Insecure SSL Versions" but I can't give an ETA on when that...
View ArticleComment by SlOrbA
Can I make some Proxy configuration with a squid I own to circumvent this issue?
View ArticleComment by SlOrbA
@chris.adams can you provide workaround SSLv3/TLSv1 enablement method for those willing to solve the issue by them selves until either Jolla or the exchange operators provide the more permanent solution?
View ArticleComment by chris.adams
Right, apparently we upgraded our SSL stack to disallow SSLv3 by default, as that has a security issue. We will look into providing an option (opt-in) to allow a particular account to use insecure SSL,...
View ArticleComment by chris.adams
Thank you for this information! We will follow up on these leads and try to keep everyone informed as to our progress.
View ArticleComment by rudi10
I suggest you continue inspecting Sailfish's ssl-stack. I got a tcpdump when trying to create an Exchange account to company server. Excange responds to SSL Client Hello packet with FIN, ACK packet...
View ArticleComment by SlOrbA
@chris.adams Have you checked my entry regarding the certificate validations on a separate Together question? I haven't seen any discussion here about why with curl request against non working exchange...
View ArticleComment by daywalker
1. Tried with wifi and cell. netw. both enabled + bluetooth disabled -> no success 2. Tried with cell. netw. enabled, wifi disabled, bluetooth disabled -> no success 3. Tried with cell. netw....
View ArticleComment by chris.adams
There are no meaningful changes in package versions between 1.1.7.28 and 1.1.9.28 - the only change is in as-daemon and that change was an icon update. So now we're investigating lower-level networking...
View ArticleComment by shertell
@daywalker you asked yesterday about resetting the database without resetting the device. Some time ago I received following advice from Jolla care to delete the accounts database. devel-su rm -rf...
View ArticleComment by shertell
I also have the same packages as @daywalker. And as for the others the creation of new account fails in credentials checking.
View ArticleComment by SlOrbA
I did earlier this week Factory reset and I have the situation as @daywalker New account creation fails in Credentials checking.
View ArticleComment by daywalker
- qmf-activesync-plugin-0.1.59-10.27.32.jolla.armv7hl - as-daemon-0.8.17-10.33.39.jolla.armv7hl - libas-common-utils-0.4.14-10.6.144.jolla.armv7hl - libas-protocol-0.5.17-10.10.122.jolla.armv7hl -...
View ArticleComment by chris.adams
@daywalker right, that's actually expected. When you create an account, it does create an exchange account, but doesn't finalise it. It attempts to connect to the remote server and ensure that...
View ArticleComment by chris.adams
Can people do the following: devel-su -p pkcon get-details qmf-activesync-plugin # expect 0.1.59 devel-su -p pkcon get-details as-daemon # expect 0.8.17 devel-su -p pkcon get-details libas-common-utils...
View ArticleComment by daywalker
just failed and same error as always... :( an empty account is created while i am in the GUI entering my credendials and server domain and address. when is leave the gui with 'cancel' the account is...
View ArticleComment by chris.adams
@daywalker uh oh... that suggests a database corruption of some kind, if deleting one account caused another to appear...
View ArticleComment by shertell
@daywalker OK, yes, I was a bit too quick. Some progress here maybe? Let us know how it turns out.
View ArticleComment by daywalker
you have to replace EXCHANGE_ACCOUNT_ID with the actual ID standing in front of the activesync account output on ag-tool list-accounts i just deleted the skype account and listed the accounts again. 1...
View ArticleComment by shertell
Hi I have 2 activesync accounts, one gmail and one imap account. In my case ag-tool list-settings EXCHANGE_ACCOUNT_ID outputs: (process:21173): accounts-glib-CRITICAL **: ag_manager_load_account:...
View ArticleComment by daywalker
@chris.adams ag-tool list-settings EXCHANGE_ACCOUNT_ID doesn't show any exchange account for me as it fails to create one. Question @ other users: Do you have any other accounts enabled? I have...
View Article
