Initial basic support for Samba Fileserver (ldapsam + nslcd). The idea is that the provider supports the minimum requirements for my fileserver as authentik as IdP. Everything is modded within the outpost, so I dont have to rebase authentik every major release...
Critical fields for samba are meant to be attributes in authentik. They need to be calculated with policies because property mappings are only for importing stuff. So the only possible solution is set the following properties as attributes in Register / Login / PW Change Flow:
- userPassword (SSHA)
- sambaNTPassword (NT)
Further the build especially for the LDAP outpost is now working on windows! No need to switch oses every time you want to develop!
This is a highly risky mod. Far from production. I do not plan to contribute these changes to authentik. I´m still learning golang and I wanna be able to freely experiment with code without being restricted from contributing guidelines. Further more this is more a learning thing than everything else. I learned so much abaut LDAP, smbd, pam, sssd, nslcd, ldif last weeks...
For docker images and stuff I use a private repo. You need to build it by yourself.
Have a nice day :).
authentik is an open-source Identity Provider (IdP) for modern SSO. It supports SAML, OAuth2/OIDC, LDAP, RADIUS, and more, designed for self-hosting from small labs to large production clusters.
Our enterprise offering is available for organizations to securely replace existing IdPs such as Okta, Auth0, Entra ID, and Ping Identity for robust, large-scale identity management.
- Docker Compose: recommended for small/test setups. See the documentation.
- Kubernetes (Helm Chart): recommended for larger setups. See the documentation and the Helm chart repository.
- AWS CloudFormation: deploy on AWS using our official templates. See the documentation.
- DigitalOcean Marketplace: one-click deployment via the official Marketplace app. See the app listing.
| Light | Dark |
|---|---|
![]() |
![]() |
![]() |
![]() |
See the Developer Documentation for information about setting up local build environments, testing your contributions, and our contribution process.
When you contribute documentation, either to accompany a code change or as a standalone contribution, please be sure to follow our documentation Style Guide.
Please see SECURITY.md.
Using authentik? We'd love to hear your story and feature your logo. Email us at hello@goauthentik.io or open a GitHub Issue/PR!



