What authentication systems does LibAuth support?
We currently support the following authentication methods and are members of the InCommon Federation and the UK Federation.
- Security Assertion Markup Language (SAML), Shibboleth, & Active Directory Federation Service (ADFS): these are by far the easiest to setup and maintain, especially if you belong to a federation such as InCommon or the UK Federation. These systems also support the use of groups for fine tuning your authentication.
- Central Authentication Services (CAS): similar to SAML, this is a cinch to set up and also supports the use of groups, as well.
- Lightweight Directory Access Protocol (LDAP): although this is supported, it's far more complicated to set up compared to SAML or CAS. If your institution has those services available, we recommend using them instead. Groups are not supported with this method.
- Standard Interchange Protocol (SIP2): if your ILS supports SIP2, you can use this to allow patrons to sign in using their library cards and PINs.Groups are not supported with this method.
- Self-hosted systems: have you designed your own custom authentication system? We can support that, too! Because these are inherently customized, though, it may be more complicated to configure than CAS, SAML, or SIP2.
- SirsiDynix Symphony: if the Symphony Web Services API is enabled for your SirsiDynix Symphony system, you can use it to authenticate via LibAuth.
- OAuth 2: you can connect to LibAuth using an OAuth 2 application.
For each method, you have the option of providing First / Last Name and Email attributes to us. This isn't required, but releasing this data to us allows us to auto-fill some forms, like the room registration forms in LibCal!
Once you've finalized your authentication method setup, you'll move over to the individual apps to configure those apps to use LibAuth authentication.