#singlesignon

0 posts0 participants0 posts today

LavX NewsOptimizing Multi-Step Login Forms for Seamless Password Manager IntegrationAs multi-step login forms become the norm, they pose challenges for password managers. This article delves into best practices for developers to enhance user experience and accessibility by ensuring c...<a href="https://news.lavx.hu/article/optimizing-multi-step-login-forms-for-seamless-password-manager-integration" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/optimizing-multi-step-login-forms-for-seamless-password-manager-integration</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://mastodon.cloud/tags/PasswordManager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PasswordManager</a> <a href="https://mastodon.cloud/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a>

Silke MeyerDer Mitschnitt und die Folien von meinem Vortrag "Keycloak - FAQ zu Ausfallsicherheit und Absicherung" bei den <a href="https://univention.social/tags/clt2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clt2025</a> sind jetzt online: <a href="https://chemnitzer.linux-tage.de/2025/de/programm/beitrag/185" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://chemnitzer.linux-tage.de/2025/de/programm/beitrag/185</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/mfa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mfa</a> <a href="https://univention.social/tags/2fa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2fa</a> <a href="https://univention.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://univention.social/tags/freiesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freiesoftware</a>

Silke MeyerDie Chemnitzer Linuxtage sind wie immer großartig! Vielen Dank für Euer Interesse am Keycloak-Vortrag und für die vielen guten Fragen und Ergänzungen! Foto: Corinna Hofmeister (Lieben Dank!)<a href="https://univention.social/tags/clt2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clt2025</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>

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>

rijoICYMI: New option to add WhatsApp to Meta’s accounts center <a href="https://ppc.land/new-option-to-add-whatsapp-to-metas-accounts-center/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ppc.land/new-option-to-add-whatsapp-to-metas-accounts-center/</a> <a href="https://frankfurt.social/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a> <a href="https://frankfurt.social/tags/Meta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meta</a> <a href="https://frankfurt.social/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialMedia</a> <a href="https://frankfurt.social/tags/CrossPosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CrossPosting</a> <a href="https://frankfurt.social/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a>

PPC LandICYMI: New option to add WhatsApp to Meta’s accounts center: Meta introduces a new option to link WhatsApp to its accounts center, enabling cross-posting and single sign-on. <a href="https://ppc.land/new-option-to-add-whatsapp-to-metas-accounts-center/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ppc.land/new-option-to-add-whatsapp-to-metas-accounts-center/</a> <a href="https://mastodon.social/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a> <a href="https://mastodon.social/tags/Meta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Meta</a> <a href="https://mastodon.social/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialMedia</a> <a href="https://mastodon.social/tags/CrossPosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CrossPosting</a> <a href="https://mastodon.social/tags/SingleSignOn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleSignOn</a>

Silke MeyerAlles Gute für das neue Jahr! 🎉 Bei uns steht im Januar der <a href="https://univention.social/@univention" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@univention</a> Summit im Mittelpunkt. Das Programm wird wieder toll! Auch mein Lieblingsthema Keycloak steht auf dem Plan: Ich bereite Euch einen Input vor zu den häufig gestellten Fragen rund um MFA, Kerberos-Integration und High Availability des IdP. Ihr kommt doch alle? <a href="https://www.univention-summit.de/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.univention-summit.de/</a><a href="https://univention.social/tags/univention" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#univention</a> <a href="https://univention.social/tags/univentionsummit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#univentionsummit</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/sso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sso</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/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a>

Silke MeyerAccess Control in Keycloak without LDAP groups: Want to restrict access to a connected service in Keycloak, but don't have an LDAP group to use as a filter? In this example, I'll show you how to assign a predefined role to specific user accounts to control access. While the use case is quite specific, this approach illustrates how you can leverage roles in Keycloak for flexible access management.<a href="https://help.univention.com/t/how-to-restrict-access-to-a-keycloak-client-to-self-registered-user-accounts/23629" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://help.univention.com/t/how-to-restrict-access-to-a-keycloak-client-to-self-registered-user-accounts/23629</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/sso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sso</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/nubus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nubus</a> <a href="https://univention.social/@univention" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@univention</a> <a href="https://univention.social/tags/iam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iam</a> <a href="https://univention.social/tags/authorization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authorization</a>

Silke MeyerEin <a href="https://univention.social/@univention" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@univention</a> -Kollege und ich fahren am Wochenende zu meiner Lieblingsveranstaltung, den Chemnitzer Linuxtagen. Für Sonntag morgen hab ich Input im Gepäck: Ich versuche mich in einem einführenden Rundumschlag zum Thema Single Sign-on für Webanwendungen. Was ist das überhaupt? Nimmt man SAML oder OIDC? Shibboleth IdP oder Keycloak? Schaut vorbei - ich freue mich!<a href="https://chemnitzer.linux-tage.de/2024/de/programm/beitrag/213" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://chemnitzer.linux-tage.de/2024/de/programm/beitrag/213</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/keycloak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keycloak</a> <a href="https://univention.social/tags/shibboleth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shibboleth</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/oidc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oidc</a> <a href="https://univention.social/tags/univention" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#univention</a> <a href="https://univention.social/tags/clt2024" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clt2024</a>

Recent searches

Search options

Administered by:

Server stats: