LDAP class - Revision history

JAL: increase limit from 6144

2016-09-01T22:33:39Z

increase limit from 6144

← Older revision		Revision as of 22:33, 1 September 2016
Line 324:		Line 324:
	For requests sent to the server, the SOUL <var>LDAP</var> client buffers		For requests sent to the server, the SOUL <var>LDAP</var> client buffers
	allow for several hundred bytes for any particular substring (for example, the text in an attribute value)		allow for several hundred bytes for any particular substring (for example, the text in an attribute value)
	and a total of ~~6144~~ bytes for any single message. </li>		and a total of 8184 bytes for any single message. </li>

	<li>To limit the length of time of a search, you set the <var>[[TIMEOUT]]</var>		<li>To limit the length of time of a search, you set the <var>[[TIMEOUT]]</var>

JAL: /* Using the Find methods */ add ID to list item

2016-09-01T21:23:55Z

Using the Find methods: add ID to list item

← Older revision		Revision as of 21:23, 1 September 2016
Line 320:		Line 320:
	A search for the surname <code>?aldo*</code> may return the names Baldock and Baldona, or it may return an empty result.		A search for the surname <code>?aldo*</code> may return the names Baldock and Baldona, or it may return an empty result.

	<li>You cannot limit the amount of the server data returned nor, say, the		<li id="limit">You cannot limit the amount of the server data returned nor, say, the
	number of entries returned, although LDAP servers will enforce their own limits.		number of entries returned, although LDAP servers will enforce their own limits.
	For requests sent to the server, the SOUL <var>LDAP</var> client buffers		For requests sent to the server, the SOUL <var>LDAP</var> client buffers

JAL: misc formatting

2016-08-31T20:16:12Z

misc formatting

Show changes

Dme: /* Working with returned values */

2016-08-31T11:48:47Z

Working with returned values

← Older revision		Revision as of 11:48, 31 August 2016
Line 180:		Line 180:
	The directory information returned from an		The directory information returned from an
	LDAP server in response to a <var class="product">Janus</var> <var>LDAP</var> <var>Find</var> call		LDAP server in response to a <var class="product">Janus</var> <var>LDAP</var> <var>Find</var> call
	is stored in a <var class~~="product">Janus</var> system <var>~~XmlDoc</var> object.		is stored in an <var>[[XmlDoc class\|XmlDoc]]</var> object.
	This object contains exactly the data strings sent from the server, in whatever case.		This object contains exactly the data strings sent from the server, in whatever case.

JAL at 23:25, 21 October 2013

2013-10-21T23:25:36Z

← Older revision		Revision as of 23:25, 21 October 2013
Line 3:		Line 3:
	(Lightweight Directory Access Protocol) directory.		(Lightweight Directory Access Protocol) directory.
	The <var>LDAP</var> class is a high level, object oriented interface to		The <var>LDAP</var> class is a high level, object oriented interface to
	client sockets that lets you write a <var class="product">~~User Language~~</var> LDAP		client sockets that lets you write a <var class="product">SOUL</var> LDAP
	request without knowledge of socket level programming or the format of LDAP requests and responses.		request without knowledge of socket level programming or the format of LDAP requests and responses.

	The <var>LDAP</var> class methods allow a <var class="product">~~User Language~~</var> program to act as an LDAP client		The <var>LDAP</var> class methods allow a <var class="product">SOUL</var> program to act as an LDAP client
	to access and retrieve directory information through an LDAP server.		to access and retrieve directory information through an LDAP server.
	The LDAP server may be running on any platform to which		The LDAP server may be running on any platform to which
Line 16:		Line 16:
	<p class="note">'''Note:'''		<p class="note">'''Note:'''
	To use <var>LDAP</var> objects under versions of Model 204 earlier than 7.5, you must have licensed <var class="product">[[Janus TCP/IP Base]]</var>, <var class="product">[[Janus Sockets]]</var>, '''and''' <var class="product">[[Janus SOAP]]</var>. Under version 7.5 and later,		To use <var>LDAP</var> objects under versions of Model 204 earlier than 7.5, you must have licensed <var class="product">[[Janus TCP/IP Base]]</var>, <var class="product">[[Janus Sockets]]</var>, '''and''' <var class="product">[[Janus SOAP]]</var>. Under version 7.5 and later,
	you do not require <var class="product">[[Janus SOAP]]</var>. </p>		you do not require <var class="product">Janus SOAP</var>. </p>

	For information about using SOUL objects, see [[~~Janus SOAP User Language Interface~~]].		For information about using SOUL objects, see [[Object oriented programming in SOUL]].

	==Feature summary==		==Feature summary==
Line 162:		Line 162:
	<li>Bind a connection and log in to an LDAP server.		<li>Bind a connection and log in to an LDAP server.
	<p>		<p>
	In your <var class="product">~~User Language~~</var> request, a single <var>[[Bind (LDAP function)\|Bind]]</var> method statement		In your <var class="product">SOUL</var> request, a single <var>[[Bind (LDAP function)\|Bind]]</var> method statement
	performs these actions.</p>		performs these actions.</p>

Line 292:		Line 292:
	The Janus <var>LDAP</var> class implements many of these filters with the		The Janus <var>LDAP</var> class implements many of these filters with the
	following Find methods:		following Find methods:
	<p class="~~code~~"><var>[[FindEQ (LDAP function)\|FindEQ]]</var>		<ul class="nobul">
	<var>[[FindStringInCommonName (LDAP function)\|FindStringInCommonName]]</var>		<li><var>[[FindEQ (LDAP function)\|FindEQ]]</var>
	<var>[[FindGE (LDAP function)\|FindGE]]</var>		<li><var>[[FindStringInCommonName (LDAP function)\|FindStringInCommonName]]</var>
	<var>[[FindLE (LDAP function)\|FindLE]]</var>		<li><var>[[FindGE (LDAP function)\|FindGE]]</var>
	<var>[[FindApprox (LDAP function)\|FindApprox]]</var>		<li><var>[[FindLE (LDAP function)\|FindLE]]</var>
	</p>		<li><var>[[FindApprox (LDAP function)\|FindApprox]]</var>
			</ul>

	The LDAP Internet RFC 1960 specifies a syntax for a string representation		The LDAP Internet RFC 1960 specifies a syntax for a string representation
Line 468:		Line 469:

	==List of LDAP methods==		==List of LDAP methods==
	The [[List of LDAP methods~~\|"List of LDAP methods"~~]] contains a complete list of the class methods.		The [[List of LDAP methods]] contains a complete list of the class methods.

	==See also==		==See also==

JAL: /* LDAP class example */

2013-06-05T20:46:20Z

LDAP class example

← Older revision		Revision as of 20:46, 5 June 2013
Line 436:		Line 436:
	Repeat Forever		Repeat Forever
	%Attrib = $READ ('What attribute for an EQ search?')		%Attrib = $READ ('What attribute for an EQ search?')
	If (%Attrib EQ '') then		If (%Attrib EQ <nowiki>''</nowiki>) then
	Loop End		Loop End
	End If		End If
	%SearchString = $READ ('What value?')		%SearchString = $READ ('What value?')
	If (%SearchString EQ '') then		If (%SearchString EQ <nowiki>''</nowiki>) then
	Loop End		Loop End
	End If		End If

JAL at 19:37, 29 May 2013

2013-05-29T19:37:39Z

← Older revision		Revision as of 19:37, 29 May 2013
Line 14:		Line 14:
	to define and start a TCP/IP <var>CLSOCK</var> port for the LDAP client to use.		to define and start a TCP/IP <var>CLSOCK</var> port for the LDAP client to use.

	'''Note:''' To use <var>LDAP</var> ~~class~~ objects, you must have licensed <var class="product">[[Janus Sockets]]</var> '''and''' <var class="product">[[Janus SOAP]]</var>.		<p class="note">'''Note:'''
	~~The Sirius object-oriented alternative to $functions is designed for~~		To use <var>LDAP</var> objects under versions of Model 204 earlier than 7.5, you must have licensed <var class="product">[[Janus TCP/IP Base]]</var>, <var class="product">[[Janus Sockets]]</var>, '''and''' <var class="product">[[Janus SOAP]]</var>. Under version 7.5 and later,
	<var class="product">Janus SOAP</var> ~~applications only, and~~ information about using ~~Sirius~~ objects is		you do not require <var class="product">[[Janus SOAP]]</var>. </p>
	~~provided in~~ [[Janus SOAP User Language Interface~~\|"Janus SOAP User Language Interface"~~]].
			For information about using SOUL objects, see [[Janus SOAP User Language Interface]].

	==Feature summary==		==Feature summary==

JAL: /* See also */

2013-04-26T15:12:32Z

JAL: /* See also */

2013-04-25T19:12:35Z

JAL at 19:10, 25 April 2013

2013-04-25T19:10:37Z

@@ Line 468: / Line 468: @@
 ==List of LDAP methods==
 The [[List of LDAP methods|"List of LDAP methods"]] contains a complete list of the class methods.
 [[Category:Janus Sockets]]

← Older revision		Revision as of 15:12, 26 April 2013
Line 471:		Line 471:
	==See also==		==See also==
	<ul>		<ul>
			<li>[[Janus Sockets User Language coding considerations]]
	<li>[[Sample Janus Sockets programs]]		<li>[[Sample Janus Sockets programs]]
	<li>Socket-level interfaces:		<li>Socket-level interfaces:

← Older revision		Revision as of 19:12, 25 April 2013
Line 481:		Line 481:
	<li>[[Email class]]		<li>[[Email class]]
	<li>[[HTTP Helper\|HTTP Helper classes]]		<li>[[HTTP Helper\|HTTP Helper classes]]
			<li>[[LDAP class]]
	<li>[[Janus FTP Server]]		<li>[[Janus FTP Server]]
	<li>[[Janus Telnet Server]]		<li>[[Janus Telnet Server]]