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 through HTTP headers. This is how main Access Manager products, like CA SiteMinder, are working. This is also how Apache authentication modules are working, so if your application is compatible with Apache authentication (often called “external authentication”), 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:

• HTTP Auth-Basic: replay Auth Basic authentication
• Form replay: replay form based authentication

Application list¶

Application	Configuration guide	HTTP headers	Specific Handler	CAS	SAML	OIDC
	ADFS				✔
	Alfresco	✔			✔
	Amazon Web Services				✔
	Apache	✔		✔	✔	✔
	Apache Apisix					✔
	AWX (Ansible Tower)				✔
	BigBlueButton					✔
	Bugzilla	✔
	Confluence				✔	✔
	Cornerstone				✔
	Discourse				✔	✔
	Django	✔
	Dokuwiki	✔
	Drupal	✔
	FusionDirectory	✔
	Gerrit					✔
	Gitlab				✔	✔
	Gitea					✔
	GLPI	✔
	Google Apps				✔
	Grafana					✔
	GRR	✔
	Apache Guacamole	✔		✔		✔
	HumHub					✔
	i-Parapheur	✔
	ITSM-NG	✔				✔
	Jitsi Meet	✔
	Liferay	✔
	LimeSurvey	✔
	Mailman					✔
	Matrix					✔
	Mattermost					✔
	Mediawiki	✔
	Mobilizon	✔
	NextCloud				✔	✔
	OBM	✔
	Odoo				✔
	Office 365				✔
	OpenCTI				✔	✔
	Publik					✔
	phpLDAPAdmin	✔
	Redmine					✔
	Rocketchat				✔
	Roundcube	✔
	SalesForce				✔
	SAP	✔			✔
	Sharepoint					✔
	simpleSAMLphp				✔
	Spring	✔
	Symfony	✔
	Sympa	✔		✔
	Tomcat	✔
	Wekan		✔
	Wiki.js		✔
	Wordpress			✔
	XWiki	✔
	Zimbra		✔