\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/media/logos/logo_abuledu.png b/build/lemonldap-ng/doc/media/logos/logo_abuledu.png
new file mode 100644
index 000000000..23c4389f1
Binary files /dev/null and b/build/lemonldap-ng/doc/media/logos/logo_abuledu.png differ
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/authldap.html b/build/lemonldap-ng/doc/pages/documentation/1.1/authldap.html
index 88343478d..50c29cc83 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/authldap.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/authldap.html
@@ -216,10 +216,16 @@ And this as mail filter:
LDAP password encoding: can allow to manage old LDAP servers using specific encoding for passwords (default: utf-8).
+
Use reset attribute: enable to use the password reset attribute. This attribute is set by LemonLDAP::NG when password was reset by mail and the user choose to generate the password (default: enabled).
+
+
Reset attribute: name of password reset attribute (default: pwdReset).
+
+
Reset value: value to set in reset attribute to activate password reset (default: TRUE).
@@ -302,4 +308,4 @@ You can add this object class to any entry of your directory.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/authslave.html b/build/lemonldap-ng/doc/pages/documentation/1.1/authslave.html
index 09cab4c22..25841460f 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/authslave.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/authslave.html
@@ -43,20 +43,20 @@
LL::NG Slave backend is a transparent backend to used when LL::NG portal is protected by another SSO:
-
Authentication: will create session without prompting any credentials (but will register client IP and creation date)
+
Authentication: will check user login in an header and create session without prompting any credentials (but will register client IP and creation date)
Users: collect datas transfered by HTTP headers by the main SSO system
-In Manager, go in General Parameters > Authentication modules and choose Null for authentication, users or password module.
+In Manager, go in General Parameters > Authentication modules and choose Slave for authentication or users module.
@@ -65,7 +65,7 @@ Then, go in Slave parameters:
Authentication level: authentication level for this module.
-
User attribute: LL::NG key to use as $_user (see bellow)
+
Header for user login: header that contains the user main login
@@ -87,4 +87,4 @@ You have then to declare HTTP
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/notifications.html b/build/lemonldap-ng/doc/pages/documentation/1.1/notifications.html
index 04c8fccfe..c60206832 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/notifications.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/notifications.html
@@ -27,63 +27,154 @@
-Since version 0.9.4, Lemonldap::NG can be used to notify some messages to users: if a user has a message, the message will be displayed when he will access to the portal. If the message contains checkboxes, the user has to check all of them else he can not access to the portal and get his session cookie.
+Since version 0.9.4, LemonLDAP::NG can be used to notify some messages to users: if a user has a message, the message will be displayed when he will access to the portal. If the message contains check boxes, the user has to check all of them else he can not access to the portal and get his session cookie.
+
+
+
+When the user accept the notification, the reference is stored in his persistent session.
-You just have to set “notification” to “activate” in the manager (or notification=1 in lemonldap-ng.ini, section “PORTAL”).
+You just have to activate Notifications in the Manager (General Parameters > Advanced Parameters > Notifications > Activation) or in lemonldap-ng.ini:
+
By default, notifications will be stored in the same database as configuration:
-* if you use “File” system and your “dirName” is set to /usr/local/lemonldap-ng/conf/, the notifications will be stored in /usr/local/lemonldap-ng/notifications/
-* if you use “DBI” system, the notifications will be stored in the same database as configuration and in a table called “notifications”. You have to create the table by yourself
-
if you use “File” system and your “dirName” is set to /usr/local/lemonldap-ng/conf/, the notifications will be stored in /usr/local/lemonldap-ng/notifications/
+
+
if you use “DBI” system, the notifications will be stored in the same database as configuration and in a table called “notifications”.
+
+
-You can change default parameters using the “notificationStorage” parameter with the same syntax as configStorage.
+
+You can change default parameters using the “notificationStorage” and “notificationStorageOptions” parameters with the same syntax as configuration storage parameters. To do this in Manager, go in General Parameters > Advanced Parameters > Notifications.
+
+The notifications module uses a wildcard to manage notifications for all users. The default value of this wilcard is allusers, but you can change it if allusers is a known identifier in your system.
+
+
+
+To change it, edit lemonldap-ng.ini:
+
+
+
[all]
+notificationWilcard= alluserscustom
+
+
+Then creating a notification for alluserscustom will display the notification for all users.
+
-New notifications can be insert using SOAP request (described in the WSDL file generated by buildPortalWSDL tool).
+New notifications can be insert using SOAP request (described in the WSDL file generated by buildPortalWSDL tool). To activate SOAP on the portal:
+
+
Enable SOAP in General parameters » Advanced parameters » SOAP
+
+
Enable Notifications SOAP service in Apache configuration:
+
+
+
# SOAP functions for notification insertion (disabled by default)
+<Location /index.pl/notification>
+ Orderdeny,allow
+ Deny from all
+ Allow from 192.168.2.0/24
+</Location>
@@ -95,23 +186,33 @@ New notifications can be insert using XML files containing:
-
”<notification>” element(s) :
+
<notification> element(s) :
-
required attributes :
+
Required attributes:
-
“date” in format YYYY-MM-DD
+
date: creation date (format YYYY-MM-DD)
-
“ref” : a reference that can be used later to know what has been notified and when
+
ref: a reference that can be used later to know what has been notified and when
-
“uid” : the user (it must correspond to the attibute set in whatToTrace parameter : uid by default)
+
uid: the user login (it must correspond to the attribute set in whatToTrace parameter, uid by default), or the wildcard string (by default: allusers) if the notification should be displayed for every user.
-
sub-elements :
+
Optional attributes:
-
<text> : paragraph to display : will be inserted in HTML page enclosed in <p class=“notifText”>…</p>
+
condition: condition to display the notification, can use all session variables.
-
<check> : paragraph to display with a checkbox : will be inserted in HTML page enclosed in <p class=“notifCheck”><input type=“checkbox/>…</p>
+
+
+
Sub elements:
+
+
<title>: title to display: will be inserted in HTML page enclosed in <h2 class=“notifText”>…</h2>
+
+
<subtitle>: subtitle to display: will be inserted in HTML page enclosed in <h2 class=“notifText”>…</h2>
+
+
<text>: paragraph to display: will be inserted in HTML page enclosed in <p class=“notifText”>…</p>
+
+
<check>: paragraph to display with a checkbox: will be inserted in HTML page enclosed in <p class=“notifCheck”><input type=“checkbox” />…</p>
@@ -121,20 +222,35 @@ Notifications are XML file
-All other elements will be removed including HTML elements like <b>;
+
All other elements will be removed including HTML elements like <b>.
+
+
+
+
+
One notification XML document can contain several notifications messages.
+
<?xmlversion="1.0"encoding="UTF-8"standalone="no"?><root><notificationuid="foo.bar"date="2009-01-27"reference="ABC">
-<text> You have been granted to access to appli-1 </text>
-<text> You have been granted to access to appli-2 </text>
-<check> I know that I can acces to appli-1 </check>
-<check> I know that I can acces to appli-2 </check>
+<title>You have new authorizations</title>
+<subtitle>Application 1</subtitle>
+<text>You have been granted to access to appli-1</text>
+<subtitle>Application 2</subtitle>
+<text>You have been granted to access to appli-2</text>
+<subtitle>Acceptation</subtitle>
+<check>I know that I can access to appli-1 </check>
+<check>I know that I can access to appli-2 </check>
+</notification>
+<notificationuid="allusers"date="2009-01-27"reference="disclaimer"condition="$ipAddr =~ /^192/">
+<title>This is your first access on this system</title>
+<text>Be a nice user and do not break it please.</text>
+<check>Of course I am not evil!</check></notification></root>
@@ -152,7 +268,8 @@ Example :
->proxy('http://auth.example.com/index.pl/notification');
-$r=$lite->newNotification('<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+$r=$lite->newNotification(
+'<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<root>
<notification uid="foo.bar" date="2009-01-27" reference="ABC">
<text> You have been granted to access to appli-1 </text>
@@ -160,18 +277,19 @@ Example :
<check> I know that I can acces to appli-1 </check>
<check> I know that I can acces to appli-2 </check>
</notification>
-</root>');
+</root>
+');if($r->fault){printSTDERR"SOAP Error: ".$r->fault->{faultstring};}else{my$res=$r->result();
- print"$res notification(s) have been inserted\";
-}
+ print"$res notification(s) have been inserted\n";
+}
@@ -180,5 +298,9 @@ Example :
You've simply to insert a notification and connect to the portal using the same UID. You will be prompted.
+
+Try also to create a global notification (to the uid “allusers”), and connect with any user, the message will be prompted.
+
+
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/parameterlist.html b/build/lemonldap-ng/doc/pages/documentation/1.1/parameterlist.html
index 8dd9e8d34..6f9542607 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/parameterlist.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/parameterlist.html
@@ -232,281 +232,320 @@ The attribute key name can be used directly in lemonldap-ng.ini or
LDAP version
ldapVersion
✔
-
Cache backend
localStorage
✔
✔
✔
+
LDAP modify password reset attribute
ldapUsePasswordResetAttribute
✔
-
Local cache
localStorage
✔
✔
✔
+
LDAP password reset attribute name
ldapPasswordResetAttribute
✔
-
Cache backend options
localStorageOptions
✔
✔
✔
+
LDAP password reset attribute true value
ldapPasswordResetAttributeValue
✔
-
Local cache parameters
localStorageOptions
✔
✔
✔
+
Cache backend
localStorage
✔
✔
✔
-
Access rules
locationRules
✔
+
Local cache
localStorage
✔
✔
✔
-
Macros
macros
✔
+
Cache backend options
localStorageOptions
✔
✔
✔
-
Body for password mail
mailBody
✔
+
Local cache parameters
localStorageOptions
✔
✔
✔
-
Body for confirmation mail
mailConfirmBody
✔
+
Access rules
locationRules
✔
-
Subject for confirmation mail
mailConfirmSubject
✔
+
Macros
macros
✔
-
Mail From address
mailFrom
✔
+
Body for password mail
mailBody
✔
-
LDAP mail search filter
mailLDAPFilter
✔
+
Body for confirmation mail
mailConfirmBody
✔
-
Subject for password mail
mailSubject
✔
+
Subject for confirmation mail
mailConfirmSubject
✔
-
URL for mail reset
mailUrl
✔
+
Mail From address
mailFrom
✔
-
Manager menu organization
managerCss
✔
+
Reply address
mailReplyTo
✔
-
Manager theme
managerCssTheme
✔
+
Mail charset
mailCharset
✔
-
LDAP Bind DN
managerDn
✔
+
LDAP mail search filter
mailLDAPFilter
✔
-
LDAP Bind Password
managerPassword
✔
+
Subject for password mail
mailSubject
✔
-
Manager skin
managerSkin
✔
+
Mail reset request timeout
mailTimeout
✔
-
Manager tree autoClose
managerTreeAutoClose
✔
+
URL for mail reset
mailUrl
✔
-
Manager tree JQuery CSS file
managerTreeJqueryCss
✔
+
Session key containing email address
mailSessionKey
✔
-
Multi overridden parameters
multi
✔
+
Manager menu organization
managerCss
✔
-
Multi values separator
multiValuesSeparator
✔
✔
✔
+
Manager theme
managerCssTheme
✔
-
Notification activation
notification
✔
+
LDAP Bind DN
managerDn
✔
-
Notification backend
notificationStorage
✔
+
LDAP Bind Password
managerPassword
✔
-
Notification backend options
notificationStorageOptions
✔
+
Manager skin
managerSkin
✔
-
Display deleted sessions
notifyDeleted
✔
+
Manager tree autoClose
managerTreeAutoClose
✔
-
Display other sessions
notifyOther
✔
+
Manager tree JQuery CSS file
managerTreeJqueryCss
✔
-
Null authentication level
nullAuthnLevel
✔
+
Multi overridden parameters
multi
✔
-
OpenID authentication level
openIdAuthnLevel
✔
+
Multi values separator
multiValuesSeparator
✔
✔
✔
-
OpenID allowed domains
openIdIDPList
✔
+
Notification activation
notification
✔
✔
-
OpenID secret token
openIdSecret
✔
+
Notification backend
notificationStorage
✔
✔
-
Password backend
passwordDB
✔
+
Notification backend options
notificationStorageOptions
✔
✔
-
Force port in redirection
port
✔
+
Notification uid for all users
notificationWildcard
✔
✔
-
Portal URL
portal
✔
✔
+
Display deleted sessions
notifyDeleted
✔
-
Anti frame protection
portalAntiFrame
✔
+
Display other sessions
notifyOther
✔
-
Allow form autocompletion
portalAutocomplete
✔
+
Null authentication level
nullAuthnLevel
✔
-
Display applications list
portalDisplayAppslist
✔
+
OpenID authentication level
openIdAuthnLevel
✔
-
Display change password module
portalDisplayChangePassword
✔
+
OpenID allowed domains
openIdIDPList
✔
-
Display logout module
portalDisplayLogout
✔
+
OpenID secret token
openIdSecret
✔
-
Display reset password form
portalDisplayResetPassword
✔
+
Password backend
passwordDB
✔
-
Open links in new window
portalOpenLinkInNewWindow
✔
+
Force port in redirection
port
✔
-
Require old password (change)
portalRequireOldPassword
✔
+
Portal URL
portal
✔
✔
-
Skin name
portalSkin
✔
+
Anti frame protection
portalAntiFrame
✔
-
User name session field
portalUserAttr
✔
+
Allow form autocompletion
portalAutocomplete
✔
-
Protection scheme
protection
✔
✔
+
Display applications list
portalDisplayAppslist
✔
-
Regular expression for random password
randomPasswordRegexp
✔
+
Display change password module
portalDisplayChangePassword
✔
-
Delay between check of local configuration
reloadTime
✔
+
Display logout module
portalDisplayLogout
✔
-
Remote cookie name
remoteCookieName
✔
+
Display reset password form
portalDisplayResetPassword
✔
-
Proxy cookie name
remoteCookieName
✔
+
Open links in new window
portalOpenLinkInNewWindow
✔
-
Remote Session backend
remoteGlobalStorage
✔
+
Require old password (change)
portalRequireOldPassword
✔
-
Remote Session backend options
remoteGlobalStorageOptions
✔
+
Skin name
portalSkin
✔
-
Remote portal
remotePortal
✔
+
User name session field
portalUserAttr
✔
-
SAML Session backend
samlStorage
✔
+
Protection scheme
protection
✔
✔
-
SAML Session backend options
samlStorageOptions
✔
+
Regular expression for random password
randomPasswordRegexp
✔
-
Cookie security
securedCookie
✔
✔
+
Delay between check of local configuration
reloadTime
✔
-
Delete other session if IP differs
singleIP
✔
+
Remote cookie name
remoteCookieName
✔
-
Delete other session
singleSession
✔
+
Proxy cookie name
remoteCookieName
✔
-
Do not allow several users for 1 IP
singleUserByIP
✔
+
Remote Session backend
remoteGlobalStorage
✔
-
SMTP server
SMTPServer
✔
+
Remote Session backend options
remoteGlobalStorageOptions
✔
-
SMTP user
SMTPAuthUser
✔
+
Remote portal
remotePortal
✔
-
SMTP password
SMTPAuthPass
✔
+
SAML Session backend
samlStorage
✔
-
SOAP activation
Soap
✔
+
SAML Session backend options
samlStorageOptions
✔
-
Proxy portal URL
soapAuthService
✔
+
Cookie security
securedCookie
✔
✔
-
Proxy session SOAP end point
soapSessionService
✔
+
Delete other session if IP differs
singleIP
✔
-
SSL authentication level
SSLAuthnLevel
✔
+
Delete other session
singleSession
✔
-
SSL map with LDAP attribute
SSLLDAPField
✔
+
Do not allow several users for 1 IP
singleUserByIP
✔
-
SSL force SSL authentication
SSLRequire
✔
+
SMTP server
SMTPServer
✔
-
SSL user field in certificate
SSLVar
✔
+
SMTP user
SMTPAuthUser
✔
-
Status module activation
status
✔
+
SMTP password
SMTPAuthPass
✔
-
Store password in session
storePassword
✔
+
SOAP activation
Soap
✔
-
Sympa mail session key
sympaMailKey
✔
+
Proxy portal URL
soapAuthService
✔
-
Sympa shared secret
sympaSecret
✔
+
Proxy session SOAP end point
soapSessionService
✔
-
Syslog facility
syslog
✔
+
SSL authentication level
SSLAuthnLevel
✔
-
Session lifetime for cronjob
timeout
✔
+
SSL map with LDAP attribute
SSLLDAPField
✔
-
Trusted domains
trustedDomains
✔
+
SSL force SSL authentication
SSLRequire
✔
-
Twitter application name
twitterAppName
✔
+
SSL user field in certificate
SSLVar
✔
-
Twitter authentication level
twitterAuthnLevel
✔
+
Status module activation
status
✔
-
Twitter application key
twitterKey
✔
+
Store password in session
storePassword
✔
-
Twitter application secret
twitterSecret
✔
+
Sympa mail session key
sympaMailKey
✔
-
User backend
userDB
✔
+
Sympa shared secret
sympaSecret
✔
-
Use redirect on error
useRedirectOnError
✔
+
Syslog facility
syslog
✔
-
Use Safe Jail
useSafeJail
✔
✔
+
Session lifetime for cronjob
timeout
✔
-
DBI Pivot from user table
userPivot
✔
+
Trusted domains
trustedDomains
✔
-
Use XForwardedFor for IP
useXForwardedForIP
✔
✔
+
Twitter application name
twitterAppName
✔
-
Data to store as REMOTE_USER (used also in Apache logs)
whatToTrace
✔
✔
+
Twitter authentication level
twitterAuthnLevel
✔
-
Zimbra account session key
zimbraAccountKey
✔
+
Twitter application key
twitterKey
✔
-
Zimbra account type
zimbraBy
✔
+
Twitter application secret
twitterSecret
✔
-
Zimbra preauthentication key
zimbraPreAuthKey
✔
+
User backend
userDB
✔
-
Zimbra local SSO URL pattern
zimbraSsoUrl
✔
+
Use redirect on error
useRedirectOnError
✔
-
Zimbra preauthentication URL
zimbraUrl
✔
+
Use Safe Jail
useSafeJail
✔
✔
+
+
+
DBI Pivot from user table
userPivot
✔
+
+
+
Use XForwardedFor for IP
useXForwardedForIP
✔
✔
+
+
+
Data to store as REMOTE_USER (used also in Apache logs)
@@ -558,4 +597,4 @@ The attribute key name can be used directly in lemonldap-ng.ini or
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/portalcustom.html b/build/lemonldap-ng/doc/pages/documentation/1.1/portalcustom.html
index 1d3eee830..8c7495457 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/portalcustom.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/portalcustom.html
@@ -115,7 +115,29 @@ ln -s ../pastel/*.tpl .
-Then you only have to write myskin/css/styles.css and add your media to myskin/images.
+We include some template files that can be customized:
+
+
+
customhead.tpl : HTML header markups (like CSS, js cinlusion)
+
+
customheader.tpl : HTML code int the header div
+
+
customfooter.tpm : HTML code in the footer div
+
+
+
+
+
+To use custom files, delete links and copy them into your skin folder:
+
+
+
+rm custom*
+cp ../pastel/custom* .
+
+
+
+Then you only have to write myskin/css/styles.css and add your media to myskin/images. Put all custom HTML code in the custom template files.
@@ -123,7 +145,7 @@ To configure your new skin in Manager, select the custom skin, and enter your sk
@@ -133,6 +155,8 @@ To configure your new skin in Manager, select the custom skin, and enter your sk
Require old password: used only in the password changing module of the menu, will check the old password before updating it
+
Hide old password: used only if the password need to be reset by the user (LDAP password policy), will hide the old password input
+
User attribute: which session attribute will be used to display Connected as in the menu
New window: open menu links in new window
@@ -149,4 +173,4 @@ To configure your new skin in Manager, select the custom skin, and enter your sk
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/resetpassword.html b/build/lemonldap-ng/doc/pages/documentation/1.1/resetpassword.html
index a04045cae..2f5ac41c6 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/resetpassword.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/resetpassword.html
@@ -39,28 +39,35 @@
Kinematics:
-
User enters his email in the password reset form
+
User enters his email (or another information) in the password reset form
-
LL::NG try to find the user in users database
+
LL::NG try to find the user in users database with the given information
A mail with a token is sent to user
The user click on the link in the mail
-
LL::NG validate the token and set a random password
+
LL::NG validate the token and propose a password change form
-
The random password is sent to user
+
The user can choose a new password or ask to generate one
+
+
The new password is sent to user
-
If LDAP backend is used, and LDAP password policy is enabled, the pwdReset flag is set to TRUE, so that the user is forced to change his password on next connection.
+
If LDAP backend is used, and LDAP password policy is enabled, the 'password reset flag is set to true when password is generated, so that the user is forced to change his password on next connection. This feature can be disabled in LDAP configuration.
+
+
+
+
+
If the user do a new password reset request but there is already a request pending, the user can ask the confirmation mail to be resent. The request validity time is a configuration parameter.
+
+The Secure Token Handler is a special Handler that create a token for each request and send it to the protected application. The real user identifier is stored in a Memcached server and the protected application can the request the Memcached server to get user identifier.
+
+
+
+This mechanism allow to do SSO on application with an unsafe link between Handler and the application, but with a safe link with the Memcached server.
+
+
+Go in Manager, Default parameters » Advanced parameters » Special handlers » Secure Token, and edit the different keys:
+
+
+
Memcached servers: addresses of Memcached servers, separated with spaces.
+
+
Token expiration: time in seconds for token expiration (remove from Memcached server).
+
+
Attribute to store: the session key that will be stored in Memcached.
+
+
Protected URLs: Regexp of URLs for which the secure token will be sent, separated by spaces
+
+
Header name: name of the HTTP header carrying the secure token.
+
+
+
+
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/start.html b/build/lemonldap-ng/doc/pages/documentation/1.1/start.html
index 57579767b..63ca139cf 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/start.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/start.html
@@ -316,7 +316,7 @@ Sessions are stored using
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/1.1/upgrade.html b/build/lemonldap-ng/doc/pages/documentation/1.1/upgrade.html
index 8dd2e73cf..0aeeca2d1 100644
--- a/build/lemonldap-ng/doc/pages/documentation/1.1/upgrade.html
+++ b/build/lemonldap-ng/doc/pages/documentation/1.1/upgrade.html
@@ -34,8 +34,63 @@
+
+You may have develop a custom skin following the skin customization documentation. In this case, you may face errors when displaying the portal, because some new template files are required with LemonLDAP::NG 1.1:
+
+
+
Custom template files:
+
+
customhead.tpl
+
+
customheader.tpl
+
+
customfooter.tpl
+
+
+
+
Yubikey form:
+
+
yubikeyform.tpl
+
+
+
+
+
+
+
+The Yubikey form should be linked like the standard template files:
+
+
+
+ln -s ../pastel/yubikeyform.tpl .
+
+
+
+Custom templates must be copied, you will then be able to add your custom content into it:
+
+
+
+We added the possibility to define conditions in notifications. This implies no change for File backend, but a little update of table structure for DBI backend:
+
+
ALTERTABLE`notifications`ADD`cond` VARCHAR( 255 )NULL AFTER `ref`
+
+
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/documentation/conferences.html b/build/lemonldap-ng/doc/pages/documentation/conferences.html
index 29e4737ae..4d03d9331 100644
--- a/build/lemonldap-ng/doc/pages/documentation/conferences.html
+++ b/build/lemonldap-ng/doc/pages/documentation/conferences.html
@@ -39,12 +39,24 @@
Joind.in
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/download.html b/build/lemonldap-ng/doc/pages/download.html
index eb07faa20..b94cd65dd 100644
--- a/build/lemonldap-ng/doc/pages/download.html
+++ b/build/lemonldap-ng/doc/pages/download.html
@@ -32,7 +32,7 @@
-
@@ -195,4 +214,4 @@ Protected sites:
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/build/lemonldap-ng/doc/pages/start.html b/build/lemonldap-ng/doc/pages/start.html
index 58732f456..bb732039f 100644
--- a/build/lemonldap-ng/doc/pages/start.html
+++ b/build/lemonldap-ng/doc/pages/start.html
@@ -283,6 +283,6 @@ LemonLDAP::NG is the first SSO softwar
-
