TiddlyWiki authorization - lots of pain
91 views
Skip to first unread message
Alex
Feb 5, 2019, 5:29:06 AM2/5/19
to TiddlyWiki
Hi,
I am running my tiddlywiki 5.1.19/node.js on a windows machine like this:
tiddlywiki.cmd path\to\wiki --listen port=XXX host=0.0.0.0 credentials=users.csv "writers=(authenticated)" root-tiddler=$:/core/save/lazy-images
The idea here is that I want a select few to be able to write to the wiki, and everyone else to read only.
Unfortunately, 9 times out of 10, even when a person enters the correct user credentials, the wiki starts in read-only mode. And once it starts in read only mode, it stays in it, unless you do something very drastic, like restarting the browser or bouncing the whole node.js back-end. I can't even say exactly what you need to do, because it is different every time - you just try all the different ways of reloading, multiple times. Very often it does not even ask for the credentials again, going to the read only mode straight away. Sometimes, it asks for the credentials, but then ends up in the read only mode nevertheless (and I do know my login details). Finally, at one point something clicks and you are in. BTW, this ./login-basic link never worked for me in this scenario.
Did anyone have similar issues?
TW is really a great thing, and I would like to share it with my colleagues, but I as it is now am afraid of doing it...
I am running my tiddlywiki 5.1.19/node.js on a windows machine like this:
tiddlywiki.cmd path\to\wiki --listen port=XXX host=0.0.0.0 credentials=users.csv "writers=(authenticated)" root-tiddler=$:/core/save/lazy-images
The idea here is that I want a select few to be able to write to the wiki, and everyone else to read only.
Unfortunately, 9 times out of 10, even when a person enters the correct user credentials, the wiki starts in read-only mode. And once it starts in read only mode, it stays in it, unless you do something very drastic, like restarting the browser or bouncing the whole node.js back-end. I can't even say exactly what you need to do, because it is different every time - you just try all the different ways of reloading, multiple times. Very often it does not even ask for the credentials again, going to the read only mode straight away. Sometimes, it asks for the credentials, but then ends up in the read only mode nevertheless (and I do know my login details). Finally, at one point something clicks and you are in. BTW, this ./login-basic link never worked for me in this scenario.
Did anyone have similar issues?
TW is really a great thing, and I would like to share it with my colleagues, but I as it is now am afraid of doing it...
TonyM
Feb 5, 2019, 6:15:48 AM2/5/19
to TiddlyWiki
Alex
I dont know the answer but are these other users from other computers or just tests of you own?. Are you using incognito mode for these different users. It can take a little more effort testing authentication from a single computer, browser or session.
Well worth thinking about
Tony
Jeremy Ruston
Feb 5, 2019, 10:11:01 AM2/5/19
to tiddl...@googlegroups.com
Hi Alex
I’ve not seen this problem before. It’s probably worth trying different browsers as their handling of basic authentication varies somewhat.
In the latest 5.1.20-prerelease at https://github.com/Jermolene/TiddlyWiki5 you can add debug-level=full to the command line to get a log of the authenticated username for each request, which may enable you to figure out if the problem is with the server or within the browser.
Best wishes
Jeremy.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1fc12f6a-356d-40b7-b24a-cc7cead00d19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Alex
Feb 5, 2019, 2:07:17 PM2/5/19
to TiddlyWiki
Hi Tony,
It is actual other users. And when I do the testing on my computer, I try different browsers.
On my computer, once I manage to log in, it is kind of OK, as the user is remembered. However, if I restart the back end, the settings are reset and then I often have to go through the hoops again.
It is actual other users. And when I do the testing on my computer, I try different browsers.
On my computer, once I manage to log in, it is kind of OK, as the user is remembered. However, if I restart the back end, the settings are reset and then I often have to go through the hoops again.
Alex
Feb 5, 2019, 2:15:05 PM2/5/19
to TiddlyWiki
Hi Jeremy,
Thanks for the advice. As I am not the bleeding edge kind of a guy when it comes to TW, I will wait till I upgrade to stable 5.1.20 and then try again with more logging.
That being said, I do use quite old browsers, as this is a corporate environment and I can not update software freely. I know different browsers have different quirks, but I thought that basic authentication is a very old standard and should be properly supported more or less everywhere .... If this is not the case, I am unpleasantly surprised ...
Thanks for the advice. As I am not the bleeding edge kind of a guy when it comes to TW, I will wait till I upgrade to stable 5.1.20 and then try again with more logging.
That being said, I do use quite old browsers, as this is a corporate environment and I can not update software freely. I know different browsers have different quirks, but I thought that basic authentication is a very old standard and should be properly supported more or less everywhere .... If this is not the case, I am unpleasantly surprised ...
Reply all
Reply to author
Forward
0 new messages