[Fedora-directory-commits] dsgw/orghtml orgchart.tmpl.in, NONE, 1.1 botframe.html, 1.1, 1.2 topframe.html.in, 1.1, 1.2

Richard Allen Megginson (rmeggins) fedora-directory-commits at redhat.com
Mon Jan 28 21:22:51 UTC 2008


Author: rmeggins

Update of /cvs/dirsec/dsgw/orghtml
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24762/dsgw/orghtml

Modified Files:
	botframe.html topframe.html.in 
Added Files:
	orgchart.tmpl.in 
Log Message:
get phonebook and orgchart working; use memmove instead of overlapping strcpy; fix memory error in dsgw_dn_parent


--- NEW FILE orgchart.tmpl.in ---
#
# BEGIN COPYRIGHT BLOCK
# This Program is free software; you can redistribute it and/or modify it under
# the terms of the GNU General Public License as published by the Free Software
# Foundation; version 2 of the License.
# 
# This Program is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
# FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
# 
# You should have received a copy of the GNU General Public License along with
# this Program; if not, write to the Free Software Foundation, Inc., 59 Temple
# Place, Suite 330, Boston, MA 02111-1307 USA.
# 
# In addition, as a special exception, Red Hat, Inc. gives You the additional
# right to link the code of this Program with code not covered under the GNU
# General Public License ("Non-GPL Code") and to distribute linked combinations
# including the two, subject to the limitations in this paragraph. Non-GPL Code
# permitted under this exception must only link to the code of this Program
# through those well defined interfaces identified in the file named EXCEPTION
# found in the source code files (the "Approved Interfaces"). The files of
# Non-GPL Code may instantiate templates or use macros or inline functions from
# the Approved Interfaces without causing the resulting work to be covered by
# the GNU General Public License. Only Red Hat, Inc. may make changes or
# additions to the list of Approved Interfaces. You must obey the GNU General
# Public License in all respects for all of the Program code and other code used
# in conjunction with the Program except the Non-GPL Code covered by this
# exception. If you modify this file, you may extend this exception to your
# version of the file, but you are not obligated to do so. If you do not wish to
# provide this exception without modification, you must delete this exception
# statement from your version and license this file solely under the GPL without
# exception. 
# 
# 
# Copyright (C) 2005 Red Hat, Inc.
# All rights reserved.
# END COPYRIGHT BLOCK
#

#############
#
#
#  Configuration file for Directory Server Org Chart
#  ----------------------------------------------------------
#
#
#############


#
#   Blank lines in this file, as well as lines that
#   start with at least one "#" character, are both ignored.
#
#
#   Name/Value pairs below are (and need to be) separated with
#   one or more tabs  (or spaces)
#
ldap-host	@host@
ldap-port	@port@
ldap-search-base	@suffix@

#
#  If you would like to have the phonebook icon visible, you must
#  supply the partial phonebook URL below, which will have each
#  given user's DN attribute value concatenated to the end.
#
#  For example, you could specify below something close to:
#
#      url-phonebook-base      http://hostname.domain.com/dsgw/bin/dosearch?context=default&hp=localhost&dn=
#

url-phonebook-base	http://@host@:@httpport@@cgiuri@/dosearch?context=pb&hp=@host@:@port@&dn=

#
#   A name that has no value after it equates to "" for the value, 
#   like the two below settings.
#
#   Not listing an entire name/value pair at all in this file
#   sets its value to "" as well.
#
#   So the below two names therefore don't even need to be in this file
#   (but are here to show them as possible options that can be changed).
#
#   Having no value below for "ldap-bind-dn" and "ldap-bind-pass"
#   indicates that you want anonymous binding to the LDAP server.
#

ldap-bind-dn	
ldap-bind-pass

#
#   Allowed values for below icon-related setting:
#
#	forefront	means show this icon next to the person's name 
#	layer		means show this icon inside the person's floating layer
#	no			means never show this icon anywhere, but MyOrgChart settings can override this setting.
#	disabled	means never show this icon. Period. So MyOrgChart will not even show this icon as a setting.
#

icons-aim-visible		disabled
icons-email-visible		layer
icons-phonebook-visible		forefront
icons-locator-visible		disabled

#
#  There is also the same concept below for a person-locator
#  type application, to show graphically where a given employee's office is located.
#  You also specify the partial URL, up until where the user's URL-
#  encoded cn value will be concatenated.
#
#	url-locator-base        http://hostname.domain.com/submit.cgi?empfullname=
#

url-locator-base	http://maps.example.com/submit2.cgi?r_loc=



#
#  This is where you specify which specific LDAP attributes
#  from your LDAP server that you would like used for both org chart
#  generation as well as final display values.
#
#  The value of the attribute specified for "attrib-job-title" will
#  be listed below anybody's name that is listed in their own box.
#  If you don't specify this setting in this file, the default used
#  will be "title".
#
#  For "attrib-farleft-rdn", this specifies which attribute you are
#  using as the leftmost RDN for the DN's of your user entries.
#

attrib-job-title    title
attrib-manager      manager
attrib-farleft-rdn  uid

#
#  This is where you specify the maximum levels that are allowed
#  to be generated for any given org chart, and the MyOrgChart version
#  of this setting will never be allowed to be higher than the below.
#
#  A "level" is defined as a reporting level, meaning that if you 
#  generate an org chart for a given director, all direct reports to him
#  (whether they have people below them or not) are level 1, people below
#  any of them are level 2, etc.
#
#  So a setting of 1 would list the full name of the user entered, and
#  then just people that directly report to that person only.
#
#  The purpose of having this configuration setting is to give you
#  control over users that may try to generate an org chart on the
#  CEO of a company, and heavily tax the LDAP server to generate
#  an org chart that may be thousands of people deep.
#
#  If this setting is not listed below, the default is 3.
#
#  The valid range of values for this setting would be a minimum of 1,
#  with no hard-coded maximum.
#

max-levels-drawn	3

#
#  The below setting relates to whether a specific assumption should be made
#  on all values that you currently have stored for your manager LDAP attribute. 
#
#  The assumption:	That all user entries are stored in LDAP on the
#			same flat level location, at least for a given
#			group of people that org charts will be generated for.
#
#  So when you enter:
#
#	Steve Jones
#
#  to generate an org chart on, which let's say equates to this DN:
#
#	uid=sjones, ou=People, dc=acme, dc=com
#
#  then should this application assume that the manager attrib value
#  of this entry is in this same location as Steve Jones:
#
#	manager =  "uid=XXXXXX, ou=People, dc=acme, dc=com" 
#
#  or is it possible that the manager's LDAP entry is at another level?
#
#
#  The below two options for this setting specifies one of two scenarios, 
#  based on how you have configured your directory information tree:
#
#
#  Either the value:
#
#	same		This means assume the same location (such as 
#			"ou=People, dc=acme, dc=com" above) that the inital
#			user entry is found at for all subsequent entries
#			involved in drawing that given org chart.
#
#			In other words, this setting assumes a totally
#			flat namespace, at least for all users that will
#			be in a given generated org chart.
#
#	search		This means there is no guarantee that other entries
#			that need to be discovered to draw the org chart
#			are in the same area of the directory tree, so when
#			searching the manager attribute DN values for a given
#			exact uid, search like this instead:  
#
#				manager = "uid=sjones,*"
#
#			This will be much more expensive of a search, so
#			if you fit this scenario, at least make sure on your LDAP
#			server that you have the substring index created for your
#			manager attribute, to make drawing the org chart as fast
#			as possible.
#
#  Default value (if this setting is not listed in this file):  same
#


manager-DN-location	same


#
#	This setting helps you configure against users entering LDAP  
#	queries for "A" or "MI" and then taxing the LDAP server by asking
#	for thousands of search results back.
#
#	The value you specify below for "min-chars-searchstring" means
#	that the user must enter AT LEAST this many characters for 
#	their request to even make it to the LDAP server.  If they type
#	less characters than this setting, they will get a message that
#	they need to enter at least X characters to search, where X will
#	be the below value.
#
#	NOTE: This setting purposely does not apply to allowing a user
#	to search for an exact UID (to avoid search results).  The logic
#	is that:
#
#	[1] Search LDAP for an equality search of (uid=XXXX), regardless
#	of both this below setting / how many characters were entered.
#
#	[2] If this single LDAP entry was not found, then make sure the
#	number of characters entered for the search are at least the below
#	number of characters, before sending a broader search to LDAP. 
#
#	If this setting is not configured below (the line is absent),
#	the default value used is 4.

min-chars-searchstring		4

#	Allowed characters in search filters.  If the user enters a search that
#	contains a character not in the allowed-filter-chars list, the user
#	will be notified the search needs to be modified.

allowed-filter-chars abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 _-


Index: botframe.html
===================================================================
RCS file: /cvs/dirsec/dsgw/orghtml/botframe.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- botframe.html	11 Jan 2008 21:58:10 -0000	1.1
+++ botframe.html	28 Jan 2008 21:22:48 -0000	1.2
@@ -57,6 +57,6 @@
 </tr>
 </table>
 <br><br>
-<tr align="center"><img src="images/starthelp.gif" border="0" alt=""></tr>
+<tr align="center"><img src="starthelp.gif" border="0" alt=""></tr>
 </body>
 </html>


Index: topframe.html.in
===================================================================
RCS file: /cvs/dirsec/dsgw/orghtml/topframe.html.in,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- topframe.html.in	11 Jan 2008 21:58:10 -0000	1.1
+++ topframe.html.in	28 Jan 2008 21:22:48 -0000	1.2
@@ -100,12 +100,12 @@
 		<span class="apptext">
 		<FORM name="form2" Method=POST action="@cgiuri@/org" target="output_window" onsubmit="return doSearch(document.form2.data.value)">
 			<font face=\"verdana, Arial, Helvetica, sans-serif\" style=\"font-size: 12px\">
-			<INPUT TYPE="TEXT" NAME="data" SIZE=20 MAXLENGTH=20>
-			<input type="submit" name="Submit" value="Go">
+				<INPUT TYPE="TEXT" NAME="data" SIZE=20 MAXLENGTH=20>
+				<input type="submit" name="Submit" value="Go">
 			</font>
-			</span>
-			</TD>
 		</FORM>
+		</span>
+		</TD>
 		</TR></TABLE>
 	</TD> 
 	<TD ALIGN=RIGHT>




More information about the Fedora-directory-commits mailing list