/[smeserver]/rpms/e-smith-horde/sme8/e-smith-horde_username.hook.patch
ViewVC logotype

Contents of /rpms/e-smith-horde/sme8/e-smith-horde_username.hook.patch

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations) (download)
Sat Feb 13 09:27:51 2010 UTC (14 years, 8 months ago) by mrjhb3
Branch: MAIN
CVS Tags: e-smith-horde-4_2_0-15_el5_sme, e-smith-horde-4_2_0-14_el5_sme, e-smith-horde-4_2_0-11_el5_sme, e-smith-horde-4_2_0-12_el5_sme, e-smith-horde-4_2_0-17_el5_sme, e-smith-horde-4_2_0-20_el5_sme, e-smith-horde-4_2_0-13_el5_sme, HEAD
Please see changelog

1 diff -Nur -x '*.orig' -x '*.rej' e-smith-horde-4.0.0/createlinks mezzanine_patched_e-smith-horde-4.0.0/createlinks
2 --- e-smith-horde-4.0.0/createlinks 2008-06-08 22:51:18.000000000 -0500
3 +++ mezzanine_patched_e-smith-horde-4.0.0/createlinks 2010-01-16 10:19:57.000000000 -0600
4 @@ -4,7 +4,7 @@
5
6 # conf-horde
7
8 -foreach (qw(conf.php prefs.php registry.php mime_drivers.php))
9 +foreach (qw(conf.php prefs.php registry.php mime_drivers.php hooks.php))
10 {
11 templates2events("/home/httpd/html/horde/config/$_", qw(
12 bootstrap-console-save
13 @@ -24,7 +24,7 @@
14 ));
15 }
16
17 -foreach (qw(registry.php prefs.php mime_drivers.php))
18 +foreach (qw(conf.php registry.php prefs.php mime_drivers.php hooks.php))
19 {
20 safe_symlink("/etc/e-smith/templates-default/template-begin-php",
21 "root/etc/e-smith/templates/home/httpd/html/horde/config/$_/template-begin");
22 @@ -73,6 +73,3 @@
23 templates2events("/etc/e-smith/sql/init/$_", $event);
24 }
25
26 -safe_symlink("/etc/e-smith/templates-default/template-begin-php",
27 - "root/etc/e-smith/templates/home/httpd/html/horde/config/conf.php/template-begin");
28 -
29 diff -Nur -x '*.orig' -x '*.rej' e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/conf.php/320Hooks mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/conf.php/320Hooks
30 --- e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/conf.php/320Hooks 2008-04-17 23:13:02.000000000 -0500
31 +++ mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/conf.php/320Hooks 2010-01-16 10:10:34.000000000 -0600
32 @@ -1,6 +1,6 @@
33 //320Hooks
34 $conf['hooks']['permsdenied'] = false;
35 -$conf['hooks']['username'] = false;
36 +$conf['hooks']['username'] = true;
37 $conf['hooks']['preauthenticate'] = false;
38 $conf['hooks']['postauthenticate'] = false;
39 $conf['hooks']['authldap'] = false;
40 diff -Nur -x '*.orig' -x '*.rej' e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/00Header mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/00Header
41 --- e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/00Header 1969-12-31 18:00:00.000000000 -0600
42 +++ mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/00Header 2010-01-16 10:16:14.000000000 -0600
43 @@ -0,0 +1,49 @@
44 +//00Header
45 +/**
46 + * Horde Hooks configuration file.
47 + *
48 + * THE HOOKS PROVIDED IN THIS FILE ARE EXAMPLES ONLY. DO NOT ENABLE THEM
49 + * BLINDLY IF YOU DO NOT KNOW WHAT YOU ARE DOING. YOU HAVE TO CUSTOMIZE THEM
50 + * TO MATCH YOUR SPECIFIC NEEDS AND SYSTEM ENVIRONMENT.
51 + *
52 + * This file is where you define any hooks, for preferences or general Horde
53 + * use, that your installation uses. The functions in this file can vastly
54 + * change how your installation behaves, so make sure to test out any changes
55 + * here before doing them in a production environment.
56 + *
57 + * Hook function names are automatically determined. The format of the name
58 + * is:
59 + *
60 + * _<type of hook>_hook_<name of hook>.
61 + *
62 + * Types of hooks that are defined in this file are 'prefs' (hooks to set the
63 + * value of preferences), 'horde' (hooks for the Horde Framework scripts) and
64 + * 'app' (where app is any Horde application name, like 'imp') hooks that are
65 + * application specific.
66 + *
67 + * So, a hook to set the preference 'theme' would be named
68 + * "_prefs_hook_theme".
69 + *
70 + * NOTE 1: Having a hook function in this file does NOT mean that the hook
71 + * will automatically be used. YOU MUST enable the hook. For preferences, set
72 + * 'hook' => true in that preferences attributes; for other hooks, there will
73 + * be a configuration option in each application's conf.php file such as
74 + * $conf['hooks']['hookname'] which must be set to true.
75 + *
76 + * NOTE 2: Preferences hooks are ONLY executed on login. Preferences are
77 + * cached during a users session and, to avoid unnecessary overhead every time
78 + * a preference is accessed, the results of hooks are cached as well. This
79 + * leads to ...
80 + *
81 + * NOTE 3: Any preference that is NOT LOCKED, that is set by a hook, WILL BE
82 + * SAVED WITH THAT VALUE. This means several things:
83 + * 1) Users will get the results of the hook set for them in their
84 + * preferences.
85 + * 2) By virtue of this, the next time they log in and load their
86 + * preferences, the hook will NOT be called, because in their last session,
87 + * we saved the results of the hook for them. However, if the preference is
88 + * locked, the result of the hook will never be saved.
89 + *
90 + * $Horde: horde/config/hooks.php.dist,v 1.73.6.19 2009-08-13 15:43:56 jan Exp $
91 + */
92 +
93 diff -Nur -x '*.orig' -x '*.rej' e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/100Username mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/100Username
94 --- e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/100Username 1969-12-31 18:00:00.000000000 -0600
95 +++ mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates/home/httpd/html/horde/config/hooks.php/100Username 2010-01-16 10:14:34.000000000 -0600
96 @@ -0,0 +1,15 @@
97 +//100Username
98 +// Here is an example _username_hook_frombackend function. It converts the user
99 +// name to all lower case. This might be necessary if an authentication backend
100 +// is case insensitive to take into account that Horde's preference system is
101 +// case sensitive.
102 +//
103 +// ex. $userID = 'MyName' returns: 'myname'
104 +
105 +if (!function_exists('_username_hook_frombackend')) \{
106 + function _username_hook_frombackend($userID)
107 + \{
108 + return String::lower($userID);
109 + \}
110 +\}
111 +
112 diff -Nur -x '*.orig' -x '*.rej' e-smith-horde-4.0.0/root/etc/e-smith/templates.metadata/home/httpd/html/horde/config/hooks.php mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates.metadata/home/httpd/html/horde/config/hooks.php
113 --- e-smith-horde-4.0.0/root/etc/e-smith/templates.metadata/home/httpd/html/horde/config/hooks.php 1969-12-31 18:00:00.000000000 -0600
114 +++ mezzanine_patched_e-smith-horde-4.0.0/root/etc/e-smith/templates.metadata/home/httpd/html/horde/config/hooks.php 2010-01-16 10:17:15.000000000 -0600
115 @@ -0,0 +1,2 @@
116 +PERMS=0640
117 +GID="www"

admin@koozali.org
ViewVC Help
Powered by ViewVC 1.2.1 RSS 2.0 feed