Monthly Downloads: 33
Programming language: Haskell
License: MIT License
Tags: Security    
Latest version: v0.2.1

wai-saml2 alternatives and similar packages

Based on the "Security" category.
Alternatively, view wai-saml2 alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of wai-saml2 or a related project?

Add another 'Security' Package



GitHub Haskell CI

A Haskell library which implements SAML2 assertion validation as WAI middleware. This can be used by a Haskell web application (the service provider, SP) to perform identity provider (IdP) initiated authentication, i.e. SAML2-based authentication where the authentication begins at the IdP-end, the IdP authenticates the user, and then gets the user to submit a SAML2 assertion back to the SP (known as "unsolicited SSO" within e.g. the Shibboleth project).


There are currently a number of limitations to this library:

  • As mentioned above, while the library implements IdP-initiated authentication, it does not yet implement SP-initiated authentication (where the SP submits a login request to the IdP).

  • The library does not currently support the full SAML2 specification and makes certain assumptions about what the IdP's responses contain. It will most likely fail with any IdPs which do not send responses in the same format. If you wish to use this library and encounter problems with your IdP, please open an issue or a pull request which implements support accordingly.

    • The library expects that SAML assertions will be encrypted and will decrypt these. There is currently no support for plain-text assertions.


The library is estimated to be sufficiently robust for use in a production environment. If you wish to implement this middleware, please note the following:

  • You must store IDs of assertions you see. If an assertion is successfully validated by this library, you must check that you have not previous seen the assertion ID in order to prevent replay attacks.

  • You must not expose any errors to a client as that could severely compromise the security of the system as attackers may be able to use the errors to narrow down valid SAML responses. You should log and monitor errors though as they may indicate attacks on your system. Ensure that log files containing errors from the SAML2 middleware are stored securely.



You need to have registered your service provider with the identity provider. You need to have access to the IdP's metadata, which will contain the public key used for signature validation.


The saml2Config function may be used to construct SAML2Config values. It expects at least the SP's private key and the IdP's public key as arguments, but you should almost certainly customise the configuration further. The private and public keys can be loaded with functions from the Data.X509 and Data.X509.File modules (from the x509 and x509-store packages, respectively):

(saml2Config spPrivateKey idpPublicKey){
    saml2AssertionPath = "/sso/assert",
    saml2ExpectedIssuer = Just "https://idp.sp.com/saml2",
    saml2ExpectedDestination = Just "https://example.com/sso/assert",

The configuration options are documented in the Haddock documentation for the Network.Wai.SAML2.Config module.


Two interfaces to the middleware are provided. See the Haddock documentation for the Network.Wai.SAML2 module for full usage examples. An example using the saml2Callback variant is shown below, where cfg is a SAML2Config value and app is your existing WAI application:

saml2Callback cfg callback mainApp
 where callback (Left err) app req sendResponse = do
           -- a POST request was made to the assertion endpoint, but
           -- something went wrong, details of which are provided by
           -- the error: this should probably be logged as it may
           -- indicate that an attack was attempted against the 
           -- endpoint, but you *must* not show the error
           -- to the client as it would severely compromise
           -- system security
           -- you may also want to return e.g. a HTTP 400 or 401 status
       callback (Right result) app req sendResponse = do   
           -- a POST request was made to the assertion endpoint and the
           -- SAML2 response was successfully validated:        
           -- you *must* check that you have not encountered the 
           -- assertion ID before; we assume that there is a
           -- computation tryRetrieveAssertion which looks up
           -- assertions by ID in e.g. a database
           result <- tryRetrieveAssertion (assertionId (assertion result))

           case result of 
               Just something -> -- a replay attack has occurred
               Nothing -> do
                   -- store the assertion id somewhere
                   storeAssertion (assertionId (assertion result))

                   -- the assertion is valid and you can now e.g.
                   -- retrieve user data from your database
                   -- before proceeding with the request by e.g.
                   -- redirecting them to the main view




*Note that all licence references and agreements mentioned in the wai-saml2 README section above are relevant to that project's source code only.