yesod-auth-ldap-native alternatives and similar packages
Based on the "yesod" category.
Alternatively, view yesod-auth-ldap-native alternatives based on common mentions on social networks and blogs.
-
-
-
-
yesod-routes-flow
DISCONTINUED. routes for typescript [GET https://api.github.com/repos/freckle/yesod-routes-flow: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository] -
yesod-dsl
A domain specific language and a code generator desined to create RESTful services for managing an RDBMS with Yesod web framework and Persistent. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
yesod-raml
Generate Yesod framework route definitions, documentaiton, mock-handler, and more from your RAML spec. -
-
-
-
-
-
-
-
-
-
-
yesod-auth-hmac-keccak
DISCONTINUED. An account authentication plugin for yesod with encrypted token transfer. -
-
yesod-datatables
Routines for implementing server-side processing for DataTables (jQuery grid) in Haskell -
-
-
-
-
yesod-form-bulma
DISCONTINUED. [GET https://api.github.com/repos/waddlaw/yesod-bulma: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository] -
-
-
-
-
-
-
-
yesod-s3
DISCONTINUED. Simple Helper Library for using Amazon's Simple Storage Service (S3) with Yesod
InfluxDB – Built for High-Performance Time Series Workloads
Do you think we are missing an alternative of yesod-auth-ldap-native or a related project?
README
yesod-auth-ldap-native
Yesod LDAP authentication plugin using native Haskell Ldap.Client
- does not depend on system libraries
- service account bind
- customizable
- optional group membership verification
There is more than one way to perform LDAP based authentication. The key thing to decide is how to map from usernames to DNs.
This module follows the service bind approach where we bind with preconfigured credentials and run queries to find user DN and optionally verify group membership. After that we bind as user to verify password.
Another common, although in some ways more limited, approach is defining DNs as templates eg. uid=%s,ou=people,dc=example,dc=com. This module does not support template based configuration. Please submit an issue or create a pull request if you'd like that.
Usage
Basic configuration in Foundation.hs:
ldapConf :: LdapAuthConf
ldapConf =
setHost (Secure "127.0.0.1") $ setPort 636
$ mkLdapConf (Just ("cn=Manager,dc=example,dc=com", "v3ryS33kret"))
"ou=people,dc=example,dc=com"
And add authLdap ldapConf to your authPlugins.
Make sure the address you provide exactly maches the one in the server certificate. Otherwise you will only get a cryptic TLS negotiation failure.
For plain connection (only for testing!):
setHost (Plain "127.0.0.1")
For additional group authentication use setGroupQuery:
ldapConf :: LdapAuthConf
ldapConf =
setGroupQuery (Just $ mkGroupQuery
"ou=group,dc=example,dc=com" "cn" "it" "memberUid")
$ setHost (Secure "127.0.0.1") $ setPort 636
$ mkLdapConf (Just ("cn=yourapp,ou=services,dc=example,dc=com", "v3ryS33kret"))
"ou=people,dc=example,dc=com"
In the example above user jdoe will only be successfully authenticated if:
- service bind using the provided account is successful
- and exactly one entry with
objectclass=posixAccountanduid=jdoeexists somewhere inou=people,dc=example,dc=com - and at least one group exists with
cn=itandmemberUid=jdoeinou=group,dc=example,dc=com - and user bind is successful
Fine control of the queries is available with setUserQuery and setGroupQuery.
When testing or during initial configuration consider using setDebug - set to 1 to enable. This will
give you exact error condition instead of "That is all we know". Never use it in production though as it
may reveal sensitive information.
API Documentation
Documentation is available on hackage.
Refer to ldap-client documentation for details.