State of authentication and identity management in Fedora
Fedora Project is often seen as a leading test bed for identity management, thanks to its close relationship with FreeIPA, SSSD, and other projects. However, we rarely talk about goals and use cases these projects are trying to solve within Fedora distributions' context. Changes happen almost in every Fedora release: authconfig replaced by authselect, SSSD providing a new Kerberos credentials cache storage, smartcards support being added and a multitude of other changes came in with FreeIPA or Samba refreshes. Still, use of new features is somewhat limited by a relative complexity of detecting and setting up actual environments.
With the addition of Fedora Silverblue, many classic desktop integration methods that are backed by FreeIPA, Samba and SSSD tools would need to be re-thought to fit immutable containerised environments.
There is also an industry-wide effort to reduce use of insecure versions of various network protocols. While there is a good progress with protocols like TLS and common security policies, ease of use for desktop users directly clashes with these activities and we need to look into how both user experience and security could be improved.
The talk is going to provide a Fedora-wide overview of the work being done by multiple teams to improve identity and authentication packaging infrastructure within Fedora projects, how individual components play together and what to expect in future.
standard talk setup is enough
This would be very useful (and a great breakout from the State of the Fedora Server, where we usually mention wanting to do more in this space but don't always have time for it in that session).
Metadata Update from @mattdm: - Issue assigned to mattdm
Metadata Update from @mattdm: - Issue marked as blocking: #223 - Issue tagged with: Talk Accepted
Metadata Update from @riecatnor: - Issue close_status updated to: Resolved - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.