handmade.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
handmade.social is for all handmade artisans to create accounts for their Etsy and other handmade business shops.

Server stats:

35
active users

#sso

0 posts0 participants0 posts today

Les mots de passe sont-ils morts ?
Quelle est la différence entre gestion des identités et gestion des accès ?
C'est quoi le 2FA, le MFA, le PasswordLess ?

🎙️ Les réponses à ces questions et bien plus, dans le nouvel épisode du podcast "Tout est sous CTRL" par Centreon !

🎧 Écoutez l'épisode maintenant sur votre plateforme préférée :
open.spotify.com/show/24LgLR47
deezer.com/fr/show/1001329601
podcasts.apple.com/us/podcast/
antennapod.org/deeplink/subscr
youtube.com/watch?v=lBR8vA8NIuE

#OpenSource#IAM#2FA
Replied in thread

IT sicher zu betreiben ist alles andere als trivial. Und einen #SSO-Dienst wie #OneLog zu betreiben erst recht verantwortungsvoll. Aber dieser Verantwortung sollte man auch nachkommen, indem man geeignete Vorsichtsmassnahmen trifft.

Vor allem aber transparent kommuniziert. Denn Transparenz hat sich nicht nur OneLog auf die Fahne geschrieben, auch das #DigitalTrustLabel der #SwissDigitalInitiative fordert das: Benachrichtigung der Betroffenen in 72h.
@adfichter
dnip.ch/2024/11/05/onelog-dark

Das Netz ist politisch · «In the darkness bind them»: Intransparenz bei OneLog - Das Netz ist politischTransparenz ist die Basis von Vertrauen und vertrauenswürdigem Journalismus. Genau diese fehlt aber rund um das «Schweizer Medien-Login», wie sich OneLog

Ive recently set up #SSO into my #kubernetes ingress layer using #traefik in my #homelab setup, and I have to say its going quite well.

Im using the keycloakopenid middleware and pointing it to my #keycloak instance.

I could then enable the middleware on all of my ingressRoutes, and traefik immediately redirects requests to the login page if a valid bearer token is not present in the request.

I had to carve out some exceptions so the keycloak admin panel is protected but the routes needed to login are still accessible anonymously.

It works well, without any fuss.

Next up I am hoping to configure the backend apps protected by this for better integration.

For example, #argoCD has SSO capabilities, and I should be able to enable them and not be promoted for a second login after the traefik layer login.

Single Sign On, #SSO, is great tech which allows centralised management of user access and authorisation. I can’t imagine the mess we’d have without it.

HOWEVER. There is an unfortunate side effect of many services implementing SSO so that user actually can’t follow where they landed. Just a form asking their credentials.

The SSO should be implemented so EXTRMELY simple manner an average user could see what happens and if they are actually on a legit page to fill in their credentials.

In my 18 years of IAM work the biggest mistake I see is rushing to secure 1 thing not all the things.

“We need SAML for AWS for <insert governance here>”

That is the wrong way to start any new or rebuilding of a IAM program or project.

The complexity of IAM is worth the time to plan.

Example: defining the source of truth, ensuring the integrity and confidentiality is critical, roles and entitlements are needed, an IdP needs to be established and tested, source of truth matches the directory, syncing the directory and IdP, implementation of authentication of the users with the IdP and MFA/ZTA configured.

All that is really important and barely enough to illustrate my point of the amount of work for that one app requires Picasso like experience with a Michelangelo touch