Changes for page Einmalanmeldung

From version < 4.1 >
edited by sas
on 20.02.2020, 14:10
To version < 5.1 >
edited by sas
on 01.07.2020, 14:01
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,7 @@
9 9  A common use case are forms used internally by some company, and that may be accessed only by the employees of that company. The user data of the active directory can be accessed via {{smallcaps}}Ntlm{{/smallcaps}}.
10 10  
11 11  {{info}}
12 -{{smallcaps}}Ntlm{{/smallcaps}}may not be available depending on your license.
12 +{{smallcaps}}Ntlm{{/smallcaps}} may not be available depending on your license.
13 13  {{/info}}
14 14  
15 15  == Using NTLM ==
... ... @@ -24,11 +24,11 @@
24 24  
25 25  The host (FQN) of the active directory controller used for authenticating users via {{smallcaps}}Ntlm{{/smallcaps}} and transmitting their data over {{smallcaps}}Ldap{{/smallcaps}}.
26 26  
27 -{{code}}
27 +{{code language="none"}}
28 28  Example: domain.example.com
29 29  {{/code}}
30 30  
31 -Connection to the {{smallcaps}}Ldap{{/smallcaps}} server for the {{smallcaps}}Ldap{{/smallcaps}}search account has been established successfully
31 +Connection to the {{smallcaps}}Ldap{{/smallcaps}} server for the {{smallcaps}}Ldap{{/smallcaps}} search account has been established successfully
32 32  
33 33  == NTLM authentication ==
34 34  
... ... @@ -38,7 +38,7 @@
38 38  
39 39  The host name of the active directory controller.
40 40  
41 -{{code}}
41 +{{code language="none"}}
42 42  Example: domain
43 43  {{/code}}
44 44  
... ... @@ -46,7 +46,7 @@
46 46  
47 47  Different forms of the domain name can be used depending on the active directory.
48 48  
49 -{{code}}
49 +{{code language="none"}}
50 50  Example: example.de oder example0
51 51  {{/code}}
52 52  
... ... @@ -92,7 +92,7 @@
92 92  
93 93  Account to be used for looking up users. It must have been granted permission to perform user lookup.
94 94  
95 -{{code}}
95 +{{code language="none"}}
96 96  Example: ldap@example.de
97 97  {{/code}}
98 98  
... ... @@ -104,7 +104,7 @@
104 104  
105 105  {{smallcaps}}Ldap{{/smallcaps}} base DN used for looking up authenticated users.
106 106  
107 -{{code}}
107 +{{code language="none"}}
108 108  Example: ou="users", dc="example", dc="de"
109 109  {{/code}}
110 110  
... ... @@ -231,11 +231,11 @@
231 231  
232 232  === Client module name ===
233 233  
234 -The name in the //login.conf// file for the client to be used, eg. {{code}}spnego-client{{/code}}.
234 +The name in the //login.conf// file for the client to be used, eg. {{code language="none"}}spnego-client{{/code}}.
235 235  
236 236  === Server module name ===
237 237  
238 -The name in the //login.conf// file for the server to be used, eg. {{code}}spnego-server{{/code}}.
238 +The name in the //login.conf// file for the server to be used, eg. {{code language="none"}}spnego-server{{/code}}.
239 239  
240 240  {{error}}
241 241  When you keep getting a HTTP 400 error with Kerberos activated, the most likely cause is that the HTTP header size of the Kerberos ticket exceeds the default header size limit of the application server, eg. Tomcat of JBoss. See the help pages on [[changing the HTTP header size limit>>doc:Formcycle.SystemSettings.TomcatSettings.LimitHTTPHeader]].
... ... @@ -249,7 +249,7 @@
249 249  
250 250  FQN (fully qualified name) and port of the active directory controller.
251 251  
252 -Example: {{code}}domain.example.com Port: 389{{/code}}
252 +Example: {{code language="none"}}domain.example.com Port: 389{{/code}}
253 253  
254 254  === SSL connection ===
255 255  
... ... @@ -257,7 +257,7 @@
257 257  
258 258  === Referral hops ===
259 259  
260 -The maximum number of referral hops that may be performed on the LDAP server. Setting this to {{code}}0{{/code}} deactivates referral hops and no references will be followed.
260 +The maximum number of referral hops that may be performed on the LDAP server. Setting this to {{code language="none"}}0{{/code}} deactivates referral hops and no references will be followed.
261 261  
262 262  === User account (with domain) ===
263 263  
... ... @@ -265,7 +265,7 @@
265 265  
266 266  {{info}}
267 267  This needs to be a username suffixed with the domain.
268 -Example: {{code}}user@EXCAMPLE.COM{{/code}}
268 +Example: {{code language="none"}}user@EXCAMPLE.COM{{/code}}
269 269  {{/info}}
270 270  
271 271  === User account password ===
... ... @@ -276,11 +276,11 @@
276 276  
277 277  The LDAP baseDN used for looking up the authenticated user.
278 278  
279 -Example: {{code}}ou="intern", dc="example", dc="com"{{/code}}
279 +Example: {{code language="none"}}ou="intern", dc="example", dc="com"{{/code}}
280 280  
281 281  == Make user data available to forms ==
282 282  
283 -The LDAP user data for the currently authenticated user are stored in the JavaScript object {{code}}window.XFC_METADATA.currentUser.ldap{{/code}} and can be accessed via JavaScript.
283 +The LDAP user data for the currently authenticated user are stored in the JavaScript object {{code language="none"}}window.XFC_METADATA.currentUser.ldap{{/code}} and can be accessed via JavaScript.
284 284  
285 285  {{info}}
286 286  The user data that will be retrieved for the current user depends on the (read) permissions of the user account used for the LDAP user lookup.
... ... @@ -294,9 +294,9 @@
294 294  try {
295 295   // Auslesen der Property und Anzeige in einem Label
296 296   var elem = $('[name=txt1]');
297 - var ldap = XFC_METADATA.currentUser.ldap;
297 + var ldap = XFC_METADATA.user.rawData;
298 298   if(ldap.hasOwnProperty('userPrincipalName')) {
299 - elem.append(ldap.userPrincipalName);
299 + elem.html(ldap.userPrincipalName);
300 300   }
301 301  } catch (err) {}
302 302  {{/code}}

Navigation

Copyright 2000-2024