<abbrtitle="LemonLDAP::NG">LL::NG</abbr> can use SAML2 to get user identity and grab some attributes defined in user profile on its Identity Provider (IDP). In this case, <abbrtitle="LemonLDAP::NG">LL::NG</abbr> acts like an SAML2 Service Provider (SP).
<p><divclass="notetip"><abbrtitle="LemonLDAP::NG">LL::NG</abbr> can also act as <ahref="../../documentation/1.9/idpsaml.html"class="wikilink1"title="documentation:1.9:idpsaml">SAML IDP</a>, that allows to interconnect two <abbrtitle="LemonLDAP::NG">LL::NG</abbr> systems.
<p><divclass="notetip">As passwords will not be managed by <abbrtitle="LemonLDAP::NG">LL::NG</abbr>, you can disable <ahref="../../documentation/1.9/portalmenu.html#menu_modules"class="wikilink1"title="documentation:1.9:portalmenu">menu password module</a>.
They are available at the EntityID <abbrtitle="Uniform Resource Locator">URL</abbr>, by default: <ahref="http://auth.example.com/saml/metadata"class="urlextern"title="http://auth.example.com/saml/metadata"rel="nofollow">http://auth.example.com/saml/metadata</a>.
In the Manager, select node <code><abbrtitle="Security Assertion Markup Language">SAML</abbr> identity providers</code> and click on <code>New identity provider</code>:
You must register IDP metadata here. You can do it either by uploading the file, or get it from IDP metadata <abbrtitle="Uniform Resource Locator">URL</abbr> (this require a network link between your server and the IDP):
<p><divclass="notetip">You can also copy/paste the metadata: just click on the Edit button. When the text is pasted, click on the Apply button to keep the value.
<liclass="level1"><divclass="li"><strong>Key name</strong>: name of the key in LemonLDAP::NG session (for example “uid” will then be used as $uid in access rules)</div>
</li>
<liclass="level1"><divclass="li"><strong>Mandatory</strong>: if set to On, then session will not open if this attribute is not given by IDP.</div>
<liclass="level1"><divclass="li"><strong>Resolution Rule</strong>: rule that will be applied to preselect an IDP for a user. You have access to all environment variable, like user <abbrtitle="Internet Protocol">IP</abbr> address.</div>
<liclass="level1"><divclass="li"><strong>NameID format</strong>: force NameID format here (email, persistent, transient, etc.). If no value, will use first NameID Format activated in metadata.</div>
</li>
<liclass="level1"><divclass="li"><strong>Force authentication</strong>: set ForceAuthn flag in authentication request</div>
</li>
<liclass="level1"><divclass="li"><strong>Passive authentication</strong>: set IsPassive flag in authentication request</div>
</li>
<liclass="level1"><divclass="li"><strong>Allow proxied authentication</strong>: allow an authentication response to be issued from another IDP that the one we register (proxy IDP). If you disallow this, you should also disallow direct login form IDP, because proxy restriction is set in authentication requests.</div>
</li>
<liclass="level1"><divclass="li"><strong>Allow login from IDP</strong>: allow a user to connect directly from an IDP link. In this case, authentication is not a response to an issued authentication request, and we have less control on conditions.</div>
<liclass="level1"><divclass="li"><strong>Requested authentication context</strong>: this context is declared in authentication request. When receiving the request, the real authentication context will be mapped ton an internal authentication level (see <ahref="../../documentation/1.9/samlservice.html#authentication_contexts"class="wikilink1"title="documentation:1.9:samlservice">how configure the mapping</a>), that you can check to allow or deny session creation.</div>
<liclass="level1"><divclass="li"><strong>Adapt session lifetime</strong>: session lifetime will be adapted from <code>SessionNotOnOrAfter</code> value found in authentication response. It means that if the IDP propose to close session earlier than the default LemonLDAP::NG timeout, the session _utime will be modified so that session is erased at the date indicated by the IDP.</div>
</li>
<liclass="level1"><divclass="li"><strong>Force UTF-8</strong>: this will force UTF-8 conversion of attributes values collected from IDP.</div>
These options override service signature options (see <ahref="../../documentation/1.9/samlservice.html#general_options"class="wikilink1"title="documentation:1.9:samlservice">SAML service configuration</a>).
<liclass="level1"><divclass="li"><strong><abbrtitle="Single Sign On">SSO</abbr> binding</strong>: force binding to use for <abbrtitle="Single Sign On">SSO</abbr> (http-redirect, http-post, etc.)</div>
<liclass="level1"><divclass="li"><strong>Encryption mode</strong>: set the encryption mode for this IDP (None, NameID or Assertion).</div>
</li>
<liclass="level1"><divclass="li"><strong>Check conditions</strong>: set to Off to disable conditions checking on authentication responses. Use with caution.</div>