Move PLA configurable items to config/pla.php
All checks were successful
Create Docker Image / Test Application (x86_64) (push) Successful in 36s
Create Docker Image / Build Docker Image (x86_64) (push) Successful in 1m22s
Create Docker Image / Build Docker Image (arm64) (push) Successful in 3m30s
Create Docker Image / Final Docker Image Manifest (push) Successful in 10s
All checks were successful
Create Docker Image / Test Application (x86_64) (push) Successful in 36s
Create Docker Image / Build Docker Image (x86_64) (push) Successful in 1m22s
Create Docker Image / Build Docker Image (arm64) (push) Successful in 3m30s
Create Docker Image / Final Docker Image Manifest (push) Successful in 10s
This commit is contained in:
@@ -72,57 +72,6 @@ return [
|
||||
'time' => env('LDAP_CACHE_TIME',5*60), // Seconds
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Support for attrs display order
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Use this array if you want to have your attributes displayed in a specific
|
||||
| order. Case is not important.
|
||||
|
|
||||
| For example, "sn" will be displayed right after "givenName". All the other
|
||||
| attributes that are not specified in this array will be displayed after in
|
||||
| alphabetical order.
|
||||
|
|
||||
*/
|
||||
|
||||
'attr_display_order' => [],
|
||||
/*
|
||||
'attr_display_order' => [
|
||||
'givenName',
|
||||
'sn',
|
||||
'cn',
|
||||
'displayName',
|
||||
'uid',
|
||||
'uidNumber',
|
||||
'gidNumber',
|
||||
'homeDirectory',
|
||||
'mail',
|
||||
'userPassword'
|
||||
],
|
||||
*/
|
||||
|
||||
/*
|
||||
* If 'login,attr' is used above such that phpLDAPadmin will search for your DN
|
||||
* at login, you may restrict the search to a specific objectClasses. EG, set this
|
||||
* to array('posixAccount') or array('inetOrgPerson',..), depending upon your
|
||||
* setup.
|
||||
*/
|
||||
'login' => [
|
||||
'attr' => [env('LDAP_LOGIN_ATTR','uid') => env('LDAP_LOGIN_ATTR_DESC','User ID')], // Attribute used to find user for login
|
||||
'objectclass' => explode(',',env('LDAP_LOGIN_OBJECTCLASS', 'posixAccount')), // Objectclass that users must contain to login
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Custom Date Format
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Configuration to determine how date fields will be displayed.
|
||||
|
|
||||
*/
|
||||
'datetime_format' => 'Y-m-d H:i:s',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Validation
|
||||
|
@@ -1,7 +1,47 @@
|
||||
<?php
|
||||
|
||||
return [
|
||||
/**
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Support for attrs display order
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Use this array if you want to have your attributes displayed in a specific
|
||||
| order. Case is not important.
|
||||
|
|
||||
| For example, "sn" will be displayed right after "givenName". All the other
|
||||
| attributes that are not specified in this array will be displayed after in
|
||||
| alphabetical order.
|
||||
|
|
||||
*/
|
||||
|
||||
'attr_display_order' => [],
|
||||
/*
|
||||
'attr_display_order' => [
|
||||
'givenName',
|
||||
'sn',
|
||||
'cn',
|
||||
'displayName',
|
||||
'uid',
|
||||
'uidNumber',
|
||||
'gidNumber',
|
||||
'homeDirectory',
|
||||
'mail',
|
||||
'userPassword'
|
||||
],
|
||||
*/
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Custom Date Format
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Configuration to determine how date fields will be displayed.
|
||||
|
|
||||
*/
|
||||
'datetime_format' => 'Y-m-d H:i:s',
|
||||
|
||||
/*
|
||||
* These attributes will be forced to MAY attributes and become optional in the
|
||||
* templates. If they are not defined in the templates, then they wont appear
|
||||
* as per normal template processing. You may want to do this because your LDAP
|
||||
@@ -13,4 +53,15 @@ return [
|
||||
# 'force_may' => ['uidNumber','gidNumber','sambaSID'],
|
||||
*/
|
||||
'force_may' => [],
|
||||
|
||||
/*
|
||||
* If 'login,attr' is used above such that phpLDAPadmin will search for your DN
|
||||
* at login, you may restrict the search to a specific objectClasses. EG, set this
|
||||
* to array('posixAccount') or array('inetOrgPerson',..), depending upon your
|
||||
* setup.
|
||||
*/
|
||||
'login' => [
|
||||
'attr' => [env('LDAP_LOGIN_ATTR','uid') => env('LDAP_LOGIN_ATTR_DESC','User ID')], // Attribute used to find user for login
|
||||
'objectclass' => explode(',',env('LDAP_LOGIN_OBJECTCLASS', 'posixAccount')), // Objectclass that users must contain to login
|
||||
],
|
||||
];
|
Reference in New Issue
Block a user