2.0.9¶

• Bad default value to display OIDC Consents tab has been fixed. The default value is now: $_oidcConsents && $_oidcConsents =~ /\w+/
• Some user log messages have been modified, check logs documentation (see also #2244)
• SAML SOAP calls are now using text/xml instead of application/xml as the MIME Content Type, as required by the SOAP standard
• Incremental lock times values can now be set in BruteForceProtection plugin through Manager. It must be a list of comma separated values. Default values are 5, 15, 60, 300, 600

/your/path/to/lemonldap-ng-cli set ldapVerify none

[configuration]
...
ldapVerify = none

2.0.8¶

• New dependency: Perl module Time::Fake is now required to run unit test and build packages, but should not be mandatory to run the software.
• Nginx configuration: some changes are required to allow IPv6, see #2152
• Option singleSessionUserByIP was removed, see #2159
• A memory leak was found in perl-fcgi with Perl < 5.18, a workaround is possible with Apache and llng-fastcgi-server, see #1314
  • With Apache: set FcgidMaxRequestsPerProcess 500 in portal virtual host
  • With llng-fastcgi-server: set PM_MAX_REQUESTS=500 in llng-fastcgi-server service configuration
• Cookie SameSite value: to avoid problems with recent browsers, SAML POST binding, LLNG cookies are now tagged as “SameSite=None”. You can change this value using manager, “SameSite=Lax” is best for installations without federations. Important note: if you’re using an unsecured connection (http:// instead of https://), “SameSite=None” will be ignored by browsers and users that already have a valid session might be prompted to login again.
• OAuth2.0 Handler: a VHost protected by the OAuth2.0 handler will now return a 401 when called without an Access Token, instead of redirecting to the portal, as specified by RFC6750
• If you encounter the following issue:

AH01630: client denied by server configuration: /usr/share/lemonldap-ng/manager/api/api.fcgi

when trying to access the portal. It probably comes from incorrect Apache configuration. Remove the (optional and disabled by default) manager API config:

rm /etc/httpd/conf.d/z-lemonldap-ng-api.conf && systemctl reload httpd

2.0.7¶

• Security:
  • #2040: Configuration of a redirection URI for an OpenID Connect Relying Party is now mandatory, as defined in the specifications. If you save your configuration, you will have an error if some of your RP don’t have a redirect URI configured.
  • #1943 / CVE-2019-19791: along with the patch provided in 2.0.7 in Lemonldap/NG/Common/PSGI/Request.pm, Apache rewrite rule must be updated to avoid an unprotected access to REST services:

portal-apache2.conf

RewriteCond "%{REQUEST_URI}" "!^/(?:(?:static|javascript|favicon).*|.*\.fcgi(?:/.*)?)$"
RewriteRule "^/(.+)$" "/index.fcgi/$1" [PT]

manager-apache2.conf

RewriteCond "%{REQUEST_URI}" "!^/(?:static|doc|lib|javascript|favicon).*"
RewriteRule "^/(.+)$" "/manager.fcgi/$1" [PT]

• Other:
  • Option checkTime was enabled by default in lemonldap-ng.ini, this let the portal check the configuration immediately instead of waiting for configuration cache expiration. You can keep this option enabled unless you need strong performances.
• Removed parameters:
  • samlIdPResolveCookie

2.0.6¶

• Option was added to display generate password box in password reset by mail plugin. If you use this feature, you must enable this option, which is disabled by default.
• If you use the default _whatToTrace macro and a case insensitive authentication backend, then a user can generate several persistent sessions for the same login (see issue 1869). This can lead to a security bug if you enabled 2FA, which rely on data stored in the persistent session. To fix this, either choose a unique attribute for _whatToTrace, either force lower case in your macro:

$_auth eq 'SAML' ? lc($_user.'@'.$_idpConfKey) : $_auth eq 'OpenIDConnect' ? lc($_user.'@'.$_oidc_OP) : lc($_user)

• On CentOS 7 / RHEL 7, a system upgrade breaks ImageMagick, which is used to display captchas (see #1951). To fix this, you can run the following commands:

yum install -y urw-base35-fonts-legacy
sed 's,/usr/share/fonts/default/Type1/,/usr/share/X11/fonts/urw-fonts/,g' -i /etc/ImageMagick/type-ghostscript.xml

2.0.5¶

• The Text::Unidecode perl module becomes a requirement (it will be automatically installed if you upgrade from from the deb or RPM repositories)
• CAS logout starts validating the service= parameter, but only if you use the CAS Access control policy. The URL sent in the service= parameter will be checked against known CAS applications, Virtual Hosts, and trusted domains. Add your target domain to trusted domains if you suddenly start having “Invalid URL” messages on logout
• Improvements in cryptographic functions: to take advantage of them, you must change the encryption key of LemonLDAP::NG (see CLI example).
• Debian packaging: FastCGI / uWsgi servers require llng-lmlog.conf and llng-lua-headers.conf. Those configuration files are now provided by lemonldap-ng-handler package and installed in /etc/nginx/snippets directory.

Upgrade order from 1.9.*¶

As usual, if you use more than 1 server and don’t want to stop SSO service AND IF YOU HAVE NO INCOMPATIBILITY MENTIONED IN THIS DOCUMENT, upgrade must be done in the following order:

1. servers with handlers only;
2. portal servers (all together if your load balancer is stateless (user or client IP) and if users use the menu);
3. manager server

Installation¶

This release of LL::NG requires these minimal versions of GNU/Linux distributions:

• Debian 9 (stretch)
• Ubuntu 16.04 LTS
• CentOS 7
• RHEL 7

For SAML features, we require at least Lasso 2.5 and we recommend Lasso 2.6.

Configuration¶

• lemonldap-ng.ini requires some new fields in portal section. Update yours using the one given installed by default. New requires fields are:
  • staticPrefix (manager and portal): the path to static content
  • templateDir (manager and portal): the path to templates directory
  • languages (manager and portal): accepted languages
• Portal skins are now in /usr/share/lemonldap-ng/portal/templates. See skin customization to adapt your templates.
• User module in authentication parameters now provides a “Same as authentication” value. You must revalidate it in the manager since all special values must be replaced by this (Multi, Choice, Proxy, Slave, SAML, OpenID,...)*
• “Multi” doesn’t exist anymore: it is replaced by Combination, a more powerful module.
• Apache and Nginx configurations must be updated to use FastCGI portal
• URLs for mail reset and register pages have changed, you must update configuration parameters. For example:

mailUrl => 'http://auth.example.com/resetpwd',
registerUrl => 'http://auth.example.com/register',

• Option trustedProxies was removed, you must now configure your Web Server to manage X-Forwarded-For header, see how to run LL::NG behind a reverse proxy.

LDAP connection¶

Now LDAP connections are kept open to improve performances. To allow that, LL::NG requires an anonymous access to LDAP RootDSE entry to check connection.

Kerberos or SSL usage¶

• A new Kerberos authentication backend has been added since 2.0. This module solves many Kerberos integration problems (usage in conjunction with other backends, better error display,…). However, you can retain the old integration manner (using Apache authentication module).
• For SSL, a new Ajax option can be used in the same idea: so SSL can be used in conjunction with other backends.

Logs¶

• Syslog: logs are now configured in lemonldap-ng.ini file only. If you use Syslog, you must reconfigure it. See logs for more.
• Apache2: Portal doesn’t use anymore Apache2 logger. Logs are always written to Apache error.log but Apache “LogLevel” parameter has no more effect on it. Portal is now a FastCGI application and doesn’t use anymore ModPerl. See logs for more.
• If you are running behind a proxy, make sure LemonLDAP::NG can see the original IP address of incoming HTTP connections

Security¶

LLNG portal now embeds the following features:

• CSRF protection (Cross-Site Request Forgery): a token is build for each form. To disable it, set requireToken to 0 (portal security parameters in the manager)
• Content-Security-Policy header: portal build dynamically this header. You can modify default values in the manager (Général parameters » Advanced parameters » Security » Content-Security-Policy)

Handlers¶

• Apache only:
  • Apache handler is now Lemonldap::NG::Handler::ApacheMP2 and Menu is now Lemonldap::NG::Handler::ApacheMP2::Menu
  • because of an Apache behaviour change, PerlHeaderParserHandler must no more be used with “reload” URLs (replaced by PerlResponseHandler). Any “reload url” that are inside a protected vhost must be unprotected in vhost rules (protection has to be done by web server configuration).
• CDA, ZimbraPreAuth, SecureToken and AuthBasic are now Handler Types. So there is no more special file to load: you just have to choose “VirtualHost type” in the manager/VirtualHosts.
• SSOCookie: Since Firefox 60 and Chrome 68, “+2d, +5M, 12h and so on...” cookie expiration time notation is no more supported. CookieExpiration value is a number of seconds until the cookie expires. A zero or negative number will expire the cookie immediately.

Rules and headers¶

• hostname() and remote_ip() are no more provided to avoid some name conflicts replaced by `$ENV{}`)
• $ENV{<cgi_variable>} is now available everywhere: see Writing rules and headers
• some variable names have changed. See Variables document

Opening conditions¶

• Rule and message fields have been swaped. You have to modifiy and validate again your access rules.

Supported servers¶

• Apache-1.3 files are not provided now. You can build them yourself by looking at Apache-2 configuration files

Ajax requests¶

Before 2.0, an Ajax query launched after session timeout received a 302 code. Now a 401 HTTP code is returned. WWW-Authenticate header contains: SSO <portal-URL>

SOAP/REST services¶

• SOAP server activation is now split in 2 parameters (configuration/sessions). You must set them else SOAP service will be disabled
• Notifications are now REST/JSON by default. You can force old format in the manager. Note that SOAP proxy has changed: http://portal/notifications now.
• If you use “adminSessions” endpoint with “singleSession*” features, you must upgrade all portals simultaneously
• SOAP services can be replaced by new REST services

CAS¶

CAS authentication module no more use perl CAS client, but our own code. You can now define several CAS servers in a specific branch in Manager, like you can define several SAML or OpenID Connect providers.

CAS issuer module has also been improved, you must modify the configuration of CAS clients to move them from virtual host branch to CAS client branch.

Developer corner¶

Portal object
  |
  +-> auth module
  |
  +-> userDB module
  |
  +-> issuer modules
  |
  +-> other plugins (notification,...)