This document describes all configuration file changes since the 2.0.0 release. This in order to keep track of all changes that were made during the 2.x release cycle.
This will help upgrades to a future 3.x release. Configuration changes during the 2.x life cycle are NOT required. Any existing configuration file will keep working!
Support permissionAttribute
configuration option for the RADIUS
authentication backend. This allows you to specify an attribute to be used for
authorization. See
documentation.
remove sessionExpireAtNight
as it is too complicated to implement correctly
in eduVPN/Let's Connect! 2.x.
We have now the showPermissions
option that takes a bool
to show/hide the
"Permission(s)" on the user's "Account" page. The default is true
.
We added the translation for Romanian (Romania). You can add it to
config.php
under supportedLanguages
to enable it in your portal:
'ro-RO' => 'română'
The sessionExpireAtNight
option (taking a boolean) has been added. Read the
docs
on how to use it.
We added the translation for Spanish (Latin America). You can add it to
config.php
under supportedLanguages
to enable it in your portal:
'es_LA' => 'español',
The FormLdapAuthentication
section also takes searchBindDn
and
searchBindPass
options now to allow binding to an LDAP server with an
account before performing the user's DN search. See
LDAP on how to use
it.
The authMethod
, supportedLanguages
and sessionExpiry
now have defaults
when the option is not specified. The authMethod
default is
FormPdoAuthentication
, the supportedLanguages
default is
['en_US' => 'English']
and the sessionExpiry
default is P90D
.
Under Api
the remoteAccessList
is ignored from now on. When remoteAccess
is set to true
the official eduVPN server_list.json
is downloaded,
validated and used to allow access from token issued by the servers listed in
that file.
The Api
section is now completely optional. The consumerList
option under
Api
is also optional now.
We now support ClientCertAuthentication
as well. It takes no configuration in
config.php
, see
CLIENT_CERT_AUTH
for how to set it up, together with web server configuration example.
The SamlAuthentication
module is removed. Use PhpSamlSpAuthentication
instead. See
PHP_SAML_SP
and
PHP_SAML_SP_UPGRADE
We added support for array
values of permissionAttribute
in the
FormLdapAuthentication
module. Until now it only took a string
. The values
of the attributes will be merged and can be used for ACLs or access to the
portal admin.
We added the translation for Portuguese (Portugal). You can add it to
config.php
under supportedLanguages
to enable it in your portal:
'pt_PT' => 'Português',
You can now set userIdAttribute
under FormLdapAuthentication
. The value of
the obtained attribute, instead of the provided "authUser" in the login form
will be used as the user ID. For example:
'userIdAttribute' => 'uid',
If not provided, the exact user ID used for binding to the LDAP server will be used as the user ID in the VPN service.
You can also specify the addRealm
option that takes a string
value that
will add a "realm" to the users specified "authUser". For example, if the user
provides foo
, an addRealm
with value example.org
would convert the
"authUser" to [email protected]
. If the user specifies [email protected]
and the
addRealm
value is example.org
nothing will be changed.
We added the translation for German (Germany). You can add it to
config.php
under supportedLanguages
to enable it in your portal:
'de_DE' => 'Deutsch',
We now support PhpSamlSpAuthentication
authentication module. It takes all
the options of SamlAuthentication
, except spEntityId
, idpMetadata
,
idpEntityId
and discoUrl
. See
PHP_SAML_SP_UPGRADE
The use of SamlAuthentication
is DEPRECATED and PhpSamlSpAuthentication
is
STILL not supported!
We added the translation for Estonian (Estonia). You can add it to
config.php
under supportedLanguages
to enable it in your portal:
'et_EE' => 'Eesti',
We added the translation for Arabic (Morocco). You can add it to config.php
under supportedLanguages
to enable it in your portal:
'ar_MA' => 'العربية',
It is now possible to completely reject users from the portal / API by requiring them to have a certain permission to get access.
The configuration option accessPermissionList
takes an array of permissions,
where the user is allowed access when they have at least one of the permissions
listed. The permissions are taken from the permissionAttribute
for the
supporting authentication backends, or from static permissions.
For example:
'accessPermissionList' => ['administrators', 'employees'],
- add
uk_UA
translation. It can be added undersupportedLanguages
as'uk_UA' => 'Українська'
- due to the update of php-saml-sp
from this version on, also the "friendly" names can be used for the
attributes instead of just the
urn:oid
variant with theSamlAuthentication
plugin. See this file for a mapping
SamlAuthentication
->permissionAttribute
also takes anarray
now, instead of only a string, to allow multiple attributes to be used.- add
pl_PL
translation. It can be added undersupportedLanguages
as'pl_PL' => 'polski'
- Add
MellonAuthentication
->nameIdSerialization
(bool
) andspEntityId
(string
) configuration options to serializeeduPersonTargetedID
to string in the same way the Shibboleth SP does this. In order to use it, thenameIdSerialization
option has to be set totrue
and thespEntityId
MUST be the entity ID of the SAML SP as configured in mod_auth_mellon