Shakedown Social

0 posts0 participants0 posts today

Silke MeyerGuten Morgen! Am 11. Juni findet wieder meine ganztägige Keycloak-Schulung statt und es gibt noch ein paar freie Plätze. Die Zielgruppe sind Admin*s, die den von <a href="https://univention.social/@univention" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@univention</a> ausgelieferten Keycloak in Verbindung mit UCS einsetzen. SSO-Vorkenntnisse sind nicht nötig. Falls noch jemand teilnehmen möchte, sind hier die Details zur Anmeldung:<a href="https://www.univention.de/training/keycloak/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.univention.de/training/keycloak/</a><a href="https://univention.social/tags/Keycloak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keycloak</a> <a href="https://univention.social/tags/singlesignon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#singlesignon</a> <a href="https://univention.social/tags/oidc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oidc</a> <a href="https://univention.social/tags/saml" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saml</a> <a href="https://univention.social/tags/univention" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#univention</a>

Silke MeyerEin kurzer Werbe-Einschub, wenn Ihr gestattet: Hab gerade gesehen, dass in "meiner" Keycloak-Schulung am 25.3. noch ein einziger Platz frei ist. Die ganztägige Schulung richtet sich an Admin*s, die den von <a href="https://univention.social/@univention" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@univention</a> ausgelieferten Keycloak in Verbindung mit UCS einsetzen. Falls noch jemand mag, sind hier die Details: <a href="https://www.univention.de/training/keycloak/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.univention.de/training/keycloak/</a><a href="https://univention.social/tags/Keycloak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keycloak</a> <a href="https://univention.social/tags/singlesignon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#singlesignon</a> <a href="https://univention.social/tags/training" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#training</a> <a href="https://univention.social/tags/schulung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#schulung</a> <a href="https://univention.social/tags/univention" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#univention</a>

Jupiter Rowland@<a href="https://io.waxandleather.com/@alisynthesis" rel="nofollow noopener noreferrer" target="_blank">Alison Wilder</a> Because if you want full-blown user rights and all the same features as a local user on all over 30,000 Fediverse instances, you need a local user account on each one of them. This means two things: <ul><li>If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.</li><li>If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.</li></ul> For one, this is utter overkill. Besides, this is technologically impossible. This would require all Fediverse instances to know all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse. And, of course, it would require a newly-launched instance to know all Fediverse users. Again, with no exception. How and from which source are they supposed to know? That said, there is a single sign-on system for the Fediverse. It's called <a href="https://magicsignon.org/page/openwebauth/home" rel="nofollow noopener noreferrer" target="_blank">OpenWebAuth</a>. It was created by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin 🖥️</a> (creator of Friendica and all its descendants) in the late 2010s already for now-defunct <a href="https://joinfediverse.wiki/The_Zotlabs_projects#Zap" rel="nofollow noopener noreferrer" target="_blank">Zap</a>, a fork (of a fork?) of <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> which, in turn, is a fork of the currently hyped Facebook alternative <a href="https://joinfediverse.wiki/Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a>. It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener noreferrer" target="_blank">streams repository</a>, got it, too. However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere. As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop. Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so. OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything. For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile. If you're logged out, and you go to my profile page, you see nothing. But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile. And all of a sudden, you see my profile. That, for example, is what OpenWebAuth is for. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zap" rel="nofollow noopener noreferrer" target="_blank">Zap</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=SingleSignOn" rel="nofollow noopener noreferrer" target="_blank">SingleSignOn</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenWebAuth" rel="nofollow noopener noreferrer" target="_blank">OpenWebAuth</a>

Kevin Karhan :verified:<a href="https://anarres.family/@alex" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alex</a> <a href="https://kind.social/@EverBeyondReach" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@EverBeyondReach</a> <a href="https://infosec.space/tags/SSO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSO</a> before <a href="https://infosec.space/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a> was even envisioned! <a href="https://infosec.space/tags/Multipass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multipass</a> <a href="https://infosec.space/tags/FifthElement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FifthElement</a> <a href="https://infosec.space/tags/Meme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meme</a> <a href="https://infosec.space/tags/LeeloDallas" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LeeloDallas</a> <a href="https://infosec.space/tags/Leelo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Leelo</a> <a href="https://infosec.space/tags/Movie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Movie</a>

Alan Martello<a href="https://vancity.social/@jon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jon</a> <a href="https://venera.social/profile/fediversenews" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fediversenews</a> <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jupiter_rowland</a> I’m slightly more optimistic. I think people are getting fed up with having all the apps: Twitter, FB, Tik-Tok, Instagram and the friction going between them all and not being able to find a friend on a given app.If the Fediverse provides less friction - through new apps that evolve to support multiple services simultaneously along with <a href="https://hachyderm.io/tags/NomadicIdentity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NomadicIdentity</a> or <a href="https://hachyderm.io/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a> - then I think folks will migrate.

Paranoid Factoid1.The first is <a href="https://mastodon.social/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a>. BUT, most of the ActivityPub services actually have SSO as an option. At the very least, Mastodon, PixelFed, PeerTube, and I think Lemmy, have an option for OpenID-Connect. And HubZilla has it's own SSO approach (which I think is also OpenID based). So it is POSSIBLE right now (or in the near term) to integrate authentication. Certainly, on the same server hosting multiple services.Account creation complexity is an impediment to adoption.

Recent searches

Search options

Administered by:

Server stats:

#singlesignon