med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

364
active users

#saml

0 posts0 participants0 posts today

Guten 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 @univention 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:

univention.de/training/keycloa

UniventionKeycloak Technikschulung | UniventionDie Schulung richtet sich an UCS-Nutzer mit Linux-Grundkenntnissen und fokussiert sich auf die praktische Anwendung von Keycloak.

I became a maintainer of a popular #SAML library for Node.js, "node-saml", which in turn uses "xml-crypto", which in turn is based on XML signatures.

If you are still using SAML for #SSO, be aware there has been string of SAML vulnerabilities related to the fundamentals of how it works and there are likely to be more. You are advised to OIDC instead.

In this thread, I'll discuss some of weaknesses in SAML that have come up repeatedly. 🧵

I'm sure there is a simple, totally obvious reason (no trusted central authority problem?) but it seems kind of strange to me that the #Fediverse doesn't allow me to truly use a single login across services via some kind of #FIDO compliant magic, considering that almost everyone is an #infosec person and/or developer. Admittedly, I haven't thought about this too deeply. Also, where's passkey support? #saml #sso

USSO is a third-party cookie-based SSO (for now), built to work across multiple domains and businesses. It has been in development for over a year by Mahdi Kiani.

Right now, it's written in Python, but a Go rewrite is coming soon. After the rewrite, OAuth, SAML, and other authentication methods will be added.

For now, USSO doesn’t have a frontend to manage all SSO operations, but everything is available through an API.

A couple of microservices also work with USSO:

A global S3-based file manager

UFAAS, a Function-as-a-Service platform, optimized for Iran

UFAAS currently only supports IRT/IRR currencies and integrates with Iranian payment gateways, but accounts can also be manually charged.

A Rust module for USSO has also been released, making it easier to integrate with Rust-based applications. Additionally, I've recently joined the development team.

USSO is planned to be used on Parch Linux, and detailed deployment documentation will be written for all major platforms, including cloud, Docker, Kubernetes, and Jails.

Mahdi Kiani on X: x.com/mahdikiani
Project GitHub: github.com/ussoio
The File Manager: github.com/ufilesorg
FaaS: github.com/ufaasio
profile manager based on usso: github.com/uprofile
rustcrate: crates.io/crates/usso

X (formerly Twitter)مهدی کیانی (@mahdikiani) on Xدر تلاش برای بنده بودن، شوهر، پدر، کمی کارآفرین با زاویه نگاه فنی
#USSO#SSO#OAuth

Im Hinblick auf den Keycloak Identity Provider kann man sich übrigens bei openDesk schön angucken, wie die verschiedenen Clients angebunden sind. Der vorkonfigurierte Keycloak ist auch ein tolles Beispiel für eine möglichst datensparsame/gezielte Freigabe von Nutzerattributen an die angebundenen Anwendungen.

gitlab.opencode.de/bmi/opendes

This is an absolutely brutal takedown of #Microsoft. How they aren't drowning in lawsuits. 🤷‍♂️

I totally understand the resistance to disabling smart card #SSO for the US govt. That's a huge change (but NYPD did it 🤔)

But MS should have been working on this non stop to help detect/mitigate. Then to outright lie about when they knew.

How any security professional could say 'well it requires access to the server' as a boundary. 😂

#SolarWinds #ADFS #InfoSec #SAML

propublica.org/article/microso

ProPublicaWhistleblower Says Microsoft Dismissed Warnings About a Security Flaw That Russians Later Used to Hack U.S. Government
More from ProPublica

A critical security flaw in GitHub Enterprise Server, known as CVE-2024-4985, allows attackers to bypass authentication and access private data. The issue lies in the SAML SSO (Security Assertion Markup Language Single Sign-On) authentication system, where attackers can send fake SAML responses that the server accepts, even if they're improperly signed. This lets them pretend to be any user, including admins, to access confidential repositories. To protect against this, it's recommended to update GitHub Enterprise Server to version 3.9.15 or later, or temporarily enable SAML certificate pinning. Additionally, monitoring access logs for unusual activities and changing passwords and SSH keys is advised.

docs.github.com/en/enterprise-

@da_667 i am testing out at around 85% which is barely enough to pass - i need to test out at 95% to have any real confidence - the last 10% is the toughest but really prospective infosec practitioners get a lot of support and everything is laid out, you just have to take a ton of sample tests and fix weak areas and keep going - psychologically it can be tough since you need a bevy of certs to really have a chance at being semi competent and well rounded but people just do need to slow down and take one step at a time, be rigorous/thorough #howtos #exercises #poc #praxis #saml #taxii #triads