Applications

How to integrate

To integrate a Web application in LL::NG, you have the following possibilities:

  • Protect the application with the Handler, and push user identity trough HTTP headers. This is how main Access Manager products, like CA SiteMinder, are working. This also how Apache authentication modules are working, so if your application is compatible with Apache authentication (often called “external authentifcation”), then you can use the Handler.
  • Specific Handler: some applications can require a specific Handler, to manage preauthentication process for example.
  • CAS: your application is a CAS client, you can configure LL::NG as a CAS server.
  • SAML: your application is a SAML Service Provider, you can configure LL::NG as a SAML Identity Provider.
  • OpenID Connect: your application is a OpenID Connect Relying Party, you can configure LL::NG as a OpenID Connect Provider.

If none of above methods is available, you can try:

Application list

HTTP headers Specific Handler CAS SAML OpenID Connect
ADFS
Alfresco
logo_amazon_web_services.jpg Amazon Web Services
Bugzilla
Cornerstone
discourse.jpg Discourse
Django
HTTP headers Specific Handler CAS SAML OpenID Connect
Dokuwiki
Drupal
fusiondirectory-logo.jpg FusionDirectory
Gitlab
GLPI
Google Apps
HTTP headers Specific Handler CAS SAML OpenID Connect
GRR
Liferay
LimeSurvey LimeSurvey
Mediawiki
NextCloud
HTTP headers Specific Handler CAS SAML OpenID Connect
OBM
Office 365
phpLDAPAdmin
Roundcube
SalesForce
SAP SAP
simpleSAMLphp
HTTP headers Specific Handler CAS SAML OpenID Connect
Spring
Symfony
Sympa
Tomcat
Wordpress
XWiki
Zimbra
HTTP headers Specific Handler CAS SAML OpenID Connect