All, WordPress permits OAuth and the standard login process logs the browser in so I believe login once and at least that browser will have access until logout, or time out.
Open ID allows you to login with a WordPress, WordPress.com account, Google, Facebook etc... It is WordPRess that has the database credentials and the API's access it on your behalf, although you could write methods to access the database directly but the database credentials will have to be out there. WordPress has a sophisticated authentication model including different access levels and more but most importantly self serve accounts, reset password features, email invitations possibly even 2FA options. There are Rest API's but I do not understand them. The advantage of leveraging the WordPress model is its pervasive, mostly free, hosted all over, extensible, responding to threats, and much much more. I think in time tiddlywiki plugins may be built to provide what services wordpress can already provide with mature technology. Custom posts (=pages) types is the way to go because ease of integration with tiddlywiki becomes possible, like editing a tiddler in WordPress as well and from a tiddlywiki. A whole range of integrations with wordpress then become possible to enable on TiddlyWiki including email sending, social sharing, linking to data feeds, rss, and much more. Regards Tony On Saturday, December 7, 2019 at 12:58:58 AM UTC+11, Arlen Beiler wrote: > > All three of those sites have an OAuth flow setup for that. Basically you > get redirected to the login page and then the login page returns a code > back to the client page. Wordpress might just involve using the browser > session, though, I’m not sure. > > On Fri, Dec 6, 2019 at 07:58 bimlas <[email protected] <javascript:>> > wrote: > >> Arlen, >> >> WordPress (that's an interesting but very feasible suggestion), Google, >>> and Github all support multi-user editing natively, so each user would have >>> their own login credentials. >>> >> >> True, but we want to access the API with the saver, so we need a Personal >> Access Token. Or is it possible to use the API with native user >> credentials? >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/9d41a1f9-5d7f-4384-8385-2689c29d0cfc%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/9d41a1f9-5d7f-4384-8385-2689c29d0cfc%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/118ebb82-8551-4fe1-98f8-e79de37bca93%40googlegroups.com.
