Folks, Increasingly, I'm wishing to make work-related TiddlyWiki files available to people who pass through the institution's authentication process.
I'm not yet even talking about multi-author here (although I had a great experience with getting set up by Jeremy to try that with a batch of students during the spring crisis semester). Rather, I need view-only access (at least) to be available to exactly those who have passed through the university's security gates. I know next-to-nothing about how an html file on a server interacts with an SSO system (there are cookies, tokens, Active Directories and ...?). (I'm not clear on whether an html file itself needs certain features, or whether a server can be configured to limit access to this or that directory of ordinary html files, showing them to all and only those who clear the SSO.) It seems to me that much is at stake for TiddlyWiki in being able to get hosted in this way. When I use my university's Microsoft Teams system, for example, I can specify a "Team" of people (each authenticated via the SSO), and then link that team to dozens of "apps" (diagrammers, databases, mind-maps, collaboration tools, project managament, kanbans, wikis [cringeworthy ones, as far as I can tell]...). Once I add content within that team's virtual content area, there's a little gated community of access to that content. I showed one of my tiddlyspot sites to my helpful IT person and asked whether the university cost host a tiddlywiki file on a server on its domain somewhere such that access would be limited to members of such a team (or in any other way mediated by our SSO's AD subsets). The response was a whole bunch of enthusiastic suggestions about available apps that I could work with *instead* -- apps that would (from her point of view) serve the same functions as TiddlyWiki. It was a sad moment. I did persuade this one person that TW is not a platform I'm about to swap out (partly by offering a tour through that tiddlyspot site, showing its versatility). But the point is that competent IT folks at institutions are oriented to the kinds of tools that function as modules within ecosystems like Teams. To be clear: the pivotal issue isn't playing with Microsoft Teams per se; it's how a tiddlywiki can be shielded by the SSO process. For certain kinds of information, a university (or other large collective) doesn't want its data living out there on an unrelated server, protected (if at all) only by a password that has nothing to do with their authentication process. Any thoughts? (If it's already possible with out-of-the-box TiddlyWiki, so long as we set up a certain server niche, I can bring the issue up with other IT specialists here, but I don't even know yet what language I'd need to be speaking to ask the right questions.) -Springer -- 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/4fce52fd-0522-43da-a8b8-1c1970d5278bo%40googlegroups.com.
