Changes for page LDAP query


From version 3.2
edited by jdr
on 29.07.2021, 16:00
Change comment: There is no comment for this version
To version 4.1
edited by sas
on 31.05.2022, 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.jdr
1 +XWiki.sas
Content
... ... @@ -10,6 +10,8 @@
10 10  
11 11  ; Use configured LDAP query?
12 12  : If this option is selected, a LDAP query preconfigured in the backend can be selected. Additionally, details about the query are displayed.
13 +; Use client LDAP connction?
14 +: If the option is selected, then the settings under Client which already defined for LDAP will be used . This means that no separate LDAP connection needs to be set up.
13 13  ; LDAP connection
14 14  : LDAP connection, which was preconfigured in the administration.
15 15  ; Base DN
... ... @@ -39,5 +39,13 @@
39 39  
40 40  ; [%$<actionname>.RESULT.rows[i]%]
41 41  : Contains the results obtained by the query in the form of a JSON array, which may contain JSON objects. The properties / attributes of a JSON object, is determined by the returned properties of the LDAP object determined in each case.
44 +: The parameter i specifies the index of the line, starting with 0 for the first row. The other attributes can be accessed using dot notation. Example RESULT:
45 +
46 +{{code language="json"}}
47 +{"rows":[{"mail":"beispiel@mail.de","name":"Beispiel"}],"rowsCount":1}
48 +{{/code}}
49 +
50 +: Access to mail via placeholder~:// [%$<Aktionsname>.RESULT.rows[0].mail%] //
51 +
42 42  ; [%$<action name>.RESULT.rowsCount%]
43 43  : Number of rows returned by the query execution. Has the value 0 if the query returned no results or an error occurred.