Hi, all! New subscriber, new user of caldavzap. Thanks for a really useful and much needed piece of software !
The main reason I need the Ajax client is to get semi-liberated from Google on a Chromebook. The users are strictly non-tech, and not having to remember yet another password is /vItal/ for the acceptance of caldav (as opposed to google calendars) . So, .. Chrome OS refuses to remember password on the calendar :/.
Pardon if this has been asked and answered here before. Tried googling "chrome password site:www.inf-it.com", but with no luck.
My google-fu came up with this though, apparently pointing out a bug in Chrome browser, with work-arounds: http://stackoverflow.com/questions/21191336/getting-chrome-to-prompt-to-save... Scroll to the end to get the latest understanding of the bug.
Anybody here with enough knowledge of Ajax to tell me how to implement this in CalDavZAP ? I'm running 0.11.1. I'm afraid most of that page is greek to me. Now would obviously bee a good time to learn AJAX, but if the solution can come from the skies to us cargo-culters that would be even better :-)
Regards, Håkon. A.
Hi Håkon,
this is not a bug, it is a feature - the username/password "save" functionality is explicitly disabled in the source code. We will add a configuration option to disable this functionality in future.
Temporarily you can remove the autocomplete="off" string from the index.html (present 2x) and then execute the cache_update.sh
JM
On 20 Oct 2014, at 15:30, Håkon Alstadheim hakon@alstadheim.priv.no wrote:
Hi, all! New subscriber, new user of caldavzap. Thanks for a really useful and much needed piece of software !
The main reason I need the Ajax client is to get semi-liberated from Google on a Chromebook. The users are strictly non-tech, and not having to remember yet another password is /vItal/ for the acceptance of caldav (as opposed to google calendars) . So, .. Chrome OS refuses to remember password on the calendar :/.
Pardon if this has been asked and answered here before. Tried googling "chrome password site:www.inf-it.com", but with no luck.
My google-fu came up with this though, apparently pointing out a bug in Chrome browser, with work-arounds: http://stackoverflow.com/questions/21191336/getting-chrome-to-prompt-to-save... Scroll to the end to get the latest understanding of the bug.
Anybody here with enough knowledge of Ajax to tell me how to implement this in CalDavZAP ? I'm running 0.11.1. I'm afraid most of that page is greek to me. Now would obviously bee a good time to learn AJAX, but if the solution can come from the skies to us cargo-culters that would be even better :-)
Regards, Håkon. A.
On 20. okt. 2014 16:21, Ján Máté wrote:
Hi Håkon,
this is not a bug, it is a feature - the username/password "save" functionality is explicitly disabled in the source code.
Ah. OK .
We will add a configuration option to disable this functionality in future.
Temporarily you can remove the autocomplete="off" string from the index.html (present 2x) and then execute the cache_update.sh
Did that now, but I'm not all there yet. Tried first setting them from "off" to "on", and that made Chrome save the password (I /think/ if it was not already there) , but still showed me the login dialog on a page reload. Lots of things cause a page reload, so it is kind of important to get to the bottom of this :/ . (I did run the script and reload apache for good measure. No joy. Tried several times).
Removing the setting entirely, removing the saved passwords in chrome and rerunning the script, restarting apache makes the passwords not even show up in "saved passwords" in chrome.
Reverting to autocomplete="on" gives still no joy, password not even saved anymore. I'm starting to think I had those passwords stored from before, when I was trying various things to get this working, like temporarily disabling javascript.
How many people are using CalDavZap with ChromeOS? (HP-chromebook 14, Norwegian locale, a few "childhood diseases" are still not over).
JM
On 20 Oct 2014, at 15:30, Håkon Alstadheim hakon@alstadheim.priv.no wrote:
Hi, all! New subscriber, new user of caldavzap. Thanks for a really useful and much needed piece of software !
The main reason I need the Ajax client is to get semi-liberated from Google on a Chromebook. The users are strictly non-tech, and not having to remember yet another password is /vItal/ for the acceptance of caldav (as opposed to google calendars) . So, .. Chrome OS refuses to remember password on the calendar :/.
Pardon if this has been asked and answered here before. Tried googling "chrome password site:www.inf-it.com", but with no luck.
My google-fu came up with this though, apparently pointing out a bug in Chrome browser, with work-arounds: http://stackoverflow.com/questions/21191336/getting-chrome-to-prompt-to-save... Scroll to the end to get the latest understanding of the bug.
Anybody here with enough knowledge of Ajax to tell me how to implement this in CalDavZAP ? I'm running 0.11.1. I'm afraid most of that page is greek to me. Now would obviously bee a good time to learn AJAX, but if the solution can come from the skies to us cargo-culters that would be even better :-)
Regards, Håkon. A.
Hi,
On 20 Oct 2014, at 17:21, Håkon Alstadheim hakon@alstadheim.priv.no wrote:
On 20. okt. 2014 16:21, Ján Máté wrote:
Hi Håkon,
this is not a bug, it is a feature - the username/password "save" functionality is explicitly disabled in the source code.
Ah. OK .
We will add a configuration option to disable this functionality in future.
Temporarily you can remove the autocomplete="off" string from the index.html (present 2x) and then execute the cache_update.sh
Did that now, but I'm not all there yet. Tried first setting them from "off" to "on", and that made Chrome save the password (I /think/ if it was not already there), but still showed me the login dialog on a page reload.
support for storing password is a browser functionality, but not showing the login page is NOT browser functionality. Cal/CardDAV usually use basic (or digest) authentication and no session cookie (or anything similar) which is usually used for "remember me" functionality (your browser sends the authorization cookie to the server, so it looks like you are automatically "logged in" without any login screen). There is no way to achieve this functionality with basic/digest auth.
Lots of things cause a page reload, so it is kind of important to get to the bottom of this :/ . (I did run the script and reload apache for good measure. No joy. Tried several times).
Removing the setting entirely, removing the saved passwords in chrome and rerunning the script, restarting apache makes the passwords not even show up in "saved passwords" in chrome.
Reverting to autocomplete="on" gives still no joy, password not even saved anymore. I'm starting to think I had those passwords stored from before, when I was trying various things to get this working, like temporarily disabling javascript.
How many people are using CalDavZap with ChromeOS? (HP-chromebook 14, Norwegian locale, a few "childhood diseases" are still not over).
Lot of users use our software because they don't like google, and if somebody not likes google he/she will not use ChromeOS :-)))
JM
Hi;
ja - ich hab die Leute eh schon darauf vorbereitet dass es sofern es dieses Feature überhaupt gibt dies nur eingeschränkt funktionieren kann....
lg gil
Am 20.10.2014 um 17:42 schrieb Ján Máté:
Hi,
On 20 Oct 2014, at 17:21, Håkon Alstadheim <hakon@alstadheim.priv.no mailto:hakon@alstadheim.priv.no> wrote:
On 20. okt. 2014 16:21, Ján Máté wrote:
Hi Håkon,
this is not a bug, it is a feature - the username/password "save" functionality is explicitly disabled in the source code.
Ah. OK .
We will add a configuration option to disable this functionality in future.
Temporarily you can remove the autocomplete="off" string from the index.html (present 2x) and then execute the cache_update.sh
Did that now, but I'm not all there yet. Tried first setting them from "off" to "on", and that made Chrome save the password (I /think/ if it was not already there), but still showed me the login dialog on a page reload.
support for storing password is a browser functionality, but not showing the login page is NOT browser functionality. Cal/CardDAV usually use basic (or digest) authentication and no session cookie (or anything similar) which is usually used for "remember me" functionality (your browser sends the authorization cookie to the server, so it looks like you are automatically "logged in" without any login screen). There is no way to achieve this functionality with basic/digest auth.
Lots of things cause a page reload, so it is kind of important to get to the bottom of this :/ . (I did run the script and reload apache for good measure. No joy. Tried several times).
Removing the setting entirely, removing the saved passwords in chrome and rerunning the script, restarting apache makes the passwords not even show up in "saved passwords" in chrome.
Reverting to autocomplete="on" gives still no joy, password not even saved anymore. I'm starting to think I had those passwords stored from before, when I was trying various things to get this working, like temporarily disabling javascript.
How many people are using CalDavZap with ChromeOS? (HP-chromebook 14, Norwegian locale, a few "childhood diseases" are still not over).
Lot of users use our software because they don't like google, and if somebody not likes google he/she will not use ChromeOS :-)))
JM
Forget my last mail... to many mail - accounts for a single brain...;)
Am 20.10.2014 um 19:36 schrieb GJ:
Hi;
ja - ich hab die Leute eh schon darauf vorbereitet dass es sofern es dieses Feature überhaupt gibt dies nur eingeschränkt funktionieren kann....
lg gil
-
GJ -
Håkon Alstadheim -
Ján Máté