External authentication for Django projects
Formal Metadata
| Title | External authentication for Django projects |
|
| Title of Series | |
| Part Number | 13 |
| Number of Parts | 173 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Jan Pazdziora - External authentication for Django projects
When applications get deployed in enterprise environment or in large
organizations, they need to support user accounts and groups that are
managed externally, in existing directory services like FreeIPA or
Active Directory, or federated via protocols like SAML. While it is
possible to add support for these individual setups and protocols
directly to application code or to Web frameworks or libraries, often
it is better to delegate the authentication and identity operations to
a frontend server and just assume that the application has to be able
to consume results of the external authentication and identity
lookups.
In this talk, we will look at Django Web framework and how with few
small changes to the framework and to the application we can extend
the functionality of existing RemoteUserMiddleware and
RemoteUserBackend to consume users coming from enterprise identity
management systems. We will focus on using proven OS-level components
such as SSSD for Web applications, but will also show setup using
federation. |
|
| Keywords | |