Changes for page Einmalanmeldung

From version 1.1 >

edited by gru
on 15.03.2019, 16:31

To version < 8.3

edited by gru
on 10.03.2021, 10:15

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1
          +1,1 @@
--$services.localization.render("PT.Main.NTLMMenue")
++Single sign-on

Content

@@ -1,20
          +1,22 @@
++//Single sign-on// for {{smallcaps}}Ntlm{{/smallcaps}} and Kerberos is a {{formcycle/}} license module which is subject to additional costs.
++
  {{content/}}
--{{figure image="FCSnapshot27.png"}}
--User interface for setting up LDAP authentication via NTLM
++{{figure image="single_sign_on_ntlm_en.png" width="600"}}
++User interface for setting up {{smallcaps}}Ldap{{/smallcaps}} authentication via {{smallcaps}}Ntlm{{/smallcaps}}. Available only if the license allows it.
  {{/figure}}
--NTLM (NT LAN Manager) can be used to authenticate users of a form.
++{{smallcaps}}Ntlm{{/smallcaps}} (NT LAN Manager) can be used to authenticate users of a form.
--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 NTLM.
++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}}.
  {{info}}
--NTLM may not be available depending on your license.
++{{smallcaps}}Ntlm{{/smallcaps}} may not be available depending on your license.
  {{/info}}
  == Using NTLM ==
--Activate this option to use NTLM.
++Activate this option to use {{smallcaps}}Ntlm{{/smallcaps}}.
  === Synchronize with {{fserver/}} ===
@@ -22,23
          +22,23 @@
  === Domain controller host ===
--The host (FQN) of the active directory controller used for authenticating users via NTLM and transmitting their data over LDAP.
++The host (FQN) of the active directory controller used for authenticating users via {{smallcaps}}Ntlm{{/smallcaps}} and transmitting their data over {{smallcaps}}Ldap{{/smallcaps}}.
--{{code}}
++{{code language="none"}}
  Example: domain.example.com
  {{/code}}
--Connection to the LDAP server for the LDAP search account has been established successfully
++Connection to the {{smallcaps}}Ldap{{/smallcaps}} server for the {{smallcaps}}Ldap{{/smallcaps}} search account has been established successfully
  == NTLM authentication ==
--The following settings are required for enabling users to authenticate via NTLM.
++The following settings are required for enabling users to authenticate via {{smallcaps}}Ntlm{{/smallcaps}}.
  === Host name of the domain controller host ===
  The host name of the active directory controller.
--{{code}}
++{{code language="none"}}
  Example: domain
  {{/code}}
@@ -46,7
          +46,7 @@
  Different forms of the domain name can be used depending on the active directory.
--{{code}}
++{{code language="none"}}
  Example: example.de oder example0
  {{/code}}
@@ -66,7
          +66,7 @@
  A computer account is recognizable by the '$' character in the domain name. e.g. example$@domain.de
  {{/info}}
--[[Help pages of //ca technologies// on creating a computer account for NTLM authentication on active directory server.>>url:https://wiki.ca.com/display/GATEWAY83/Creating+a+Computer+Account+for+NTLM+Authentication||rel="__blank" title="Creating a Computer Account for NTLM Authentication"]]
++Help pages of ca technologies on [[creating a computer account for NTLM authentication on active directory server.>>https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-3/policy-assertions/assertion-palette/access-control-assertions/require-ntlm-authentication-credentials-assertion/creating-a-computer-account-for-ntlm-authentication.html||rel="__blank" title="Creating a Computer Account for NTLM Authentication"]]
  === computer account password ===
@@ -74,15
          +74,15 @@
  == LDAP user lookup ==
--The following settings concern the user lookup after a successful NTLM authenication.
++The following settings concern the user lookup after a successful {{smallcaps}}Ntlm{{/smallcaps}} authenication.
  === Port ===
--The port for connecting to the LDAP server for the user lookup.
++The port for connecting to the {{smallcaps}}Ldap{{/smallcaps}} server for the user lookup.
  === SSL encryption ===
--Enables SSL encryption when communicating the the LDAP server.
++Enables SSL encryption when communicating the the {{smallcaps}}Ldap{{/smallcaps}} server.
  === Hop count ===
@@ -92,7
          +92,7 @@
  Account to be used for looking up users.  It must have been granted permission to perform user lookup.
--{{code}}
++{{code language="none"}}
  Example: ldap@example.de
  {{/code}}
@@ -102,8
          +102,204 @@
  === Base DN für user lookup ===
--LDAP base DN used for looking up authenticated users.
++{{smallcaps}}Ldap{{/smallcaps}} base DN used for looking up authenticated users.
--{{code}}
++{{code language="none"}}
  Example: ou="users", dc="example", dc="de"
  {{/code}}
++
++
++
++== Settings for Kerberos authentication ==
++
++{{figure image="single_sign_on_kerberos_en.png" width="600"}}
++User interface for editing the settings for Kerberos authentication. Available only when the license includes this option.
++{{/figure}}
++
++Kerberos can be used to authenticate form users. This is often used for internal forms meant only for the employees of a company. The data of the current user can be retrieved from an active directory as well.
++
++Kerberos authentication is available only when the license includes this option.
++
++=== Use Kerberos ===
++
++Activate this switch to enable Kerberos authentication.
++
++=== Synchronize with frontend server ===
++
++When activated, all changes to the configuration will be sent to all available frontend servers.
++
++=== Username ===
++
++The Window Domain account required for accessing the Key Distribution Center (KDC) and beginning the authentication process.
++
++Normally this is the user account of the active directory that is setup as a service account.
++
++{{info}}
++When no //default_realm// has been specified in the section //[libdefaults]// of the file //krb5.conf//, you will need to enter the username with a domain (FQDN).
++Example: user@EXCAMPLE.COM
++{{/info}}
++
++{{info}}
++To this user you must, in Active Directory for example, register the Domians to be used as ServiePrincipalName beginning with the service class HTTP. You can find more information [[here>>https://social.technet.microsoft.com/wiki/contents/articles/717.service-principal-names-spn-setspn-syntax.aspx||target="_blank"]] or [[here>>https://docs.microsoft.com/en-us/windows-server/networking/sdn/security/kerberos-with-spn||target="_blank"]].
++{{/info}}
++
++(% class="wikigeneratedid" %)
++=== Password ===
++
++Password of the service account.
++
++=== File krb5.conf ===
++
++Enter the content of the file //krb5.conf//, ie. the configuration file for Kerberos.
++
++Among other settings, the available encryption methods, the current real and its mapping to a KDC should be set.
++
++==== File structure ====
++
++The file format is similar to Windows INI files. It contains of individual sections, introduced by their names in brackets. Each section may or may not contain several key-value pairs:
++
++{{code language="javascript" title=""}}
++foo = bar
++{{/code}}
++
++or
++
++{{code language="javascript" title=""}}
++foobar = {
++    foo = bar
++    some = input
++}
++{{/code}}
++
++==== Section names ====
++
++* {{litem title="[libdefaults]"}} Contains settings used by the Kerberos library v5.{{/litem}}
++* {{litem title="[realms]~}~} Realm-specific settings and contact information.{{/litem~}~}
++* {{litem title="}}A list of supported session key encryption methods that should be requested by the client when performing an AS (authentication server) request. The priority of each method is given by the order in which they have been specified, the first one being the method with the highest priority. Several methods can be separated with commas or spaces.{{/litem}}
++* ~{~{litem title="default_tgs_enctypes}}A list of supported session key encryption methods that should be requested by the client when performing a TGS (ticket granting server) request. The priority of each method is given by the order in which they have been specified, the first one being the method with the highest priority. Several methods can be separated with commas or spaces.~{~{/litem}}
++* {{litem title="permitted_enctypes"}}: A list of all allowed session key encryption methods.{{/litem}}
++
++A simple configuration for the //[libdefaults]// section might look as follows:
++
++{{code language="javascript" title=""}}
++[libdefaults]
++ default_realm = EXAMPLE.COM
++ default_tkt_enctypes = aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 des3-cbc-sha1 arcfour-hmac-md5 camellia256-cts-cmac camellia128-cts-cmac des-cbc-crc des-cbc-md5 des-cbc-md4
++ default_tgs_enctypes = aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 des3-cbc-sha1 arcfour-hmac-md5 camellia256-cts-cmac camellia128-cts-cmac des-cbc-crc des-cbc-md5 des-cbc-md4
++ permitted_enctypes   = aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 des3-cbc-sha1 arcfour-hmac-md5 camellia256-cts-cmac camellia128-cts-cmac des-cbc-crc des-cbc-md5 des-cbc-md4
++{{/code}}
++
++===== [realms] =====
++
++Each key in the //[realms]// section represents the name of a Kerberos realm. The value is a list of mappings, defining the properties of each realm. The following properties can be set:
++
++* kdc: The name or address of a server running a KDC (key distribution center) for this realm, usually the server with the active directory. When necessary, the port number can be specified by appending it separated by a column.
++
++A simple configuration for the //[realms]// section might look as follows:
++
++{{code language="javascript" title=""}}
++[realms]
++   EXAMPLE.COM = {
++ kdc = domain.example.com
++   }
++{{/code}}
++
++===== [domain_realm] =====
++
++The section //[domain_realm]// contains a mapping from domain names or host names to Kerberos realm names. The key can be a host or domain name, but domain names must be prefixed with a period. The value must be the name of a Kerberos realm for this host or domain. Host and domain names should be spelled with lower case letters.
++
++A simple configuration for the //[domain_realm]// section might look as follows:
++
++{{code language="javascript" title=""}}
++[domain_realm]
++   .example.com = EXAMPLE.COM
++{{/code}}
++
++=== File login.conf ===
++
++The content of the file //login.conf//, which contains login-related settings such as the authentication method between clients and servers.
++
++A sample configuration might look as follows:
++
++{{code language="java" title=""}}
++spnego-client {
++   com.sun.security.auth.module.Krb5LoginModule required;
++};
++
++spnego-server {
++   com.sun.security.auth.module.Krb5LoginModule required
++   refreshKrb5Config=true
++   storeKey=true
++   isInitiator=false;
++};
++{{/code}}
++
++=== Client module name ===
++
++The name in the //login.conf// file for the client to be used, eg. {{code language="none"}}spnego-client{{/code}}.
++
++=== Server module name ===
++
++The name in the //login.conf// file for the server to be used, eg. {{code language="none"}}spnego-server{{/code}}.
++
++{{error}}
++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]].
++{{/error}}
++
++== LDAP user search ==
++
++The following settings are required to retrieve information about the authenticated user from an {{smallcaps}}Ldap{{/smallcaps}} (MS active directory). This data is then available in the form and can be accessed by JavaScript code.
++
++=== Domain controller host ===
++
++FQN (fully qualified name) and port of the active directory controller.
++
++Example: {{code language="none"}}domain.example.com Port: 389{{/code}}
++
++=== SSL connection ===
++
++When activated, all communications with the LDAP server will be encrypted with SSL.
++
++=== Referral hops ===
++
++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.
++
++=== User account (with domain) ===
++
++This account must have been granted permission to send search queries to the active directory.
++
++{{info}}
++This needs to be a username suffixed with the domain.
++Example: {{code language="none"}}user@EXCAMPLE.COM{{/code}}
++{{/info}}
++
++=== User account password ===
++
++Password for the user account.
++
++=== Base DN for user lookup ===
++
++The LDAP baseDN used for looking up the authenticated user.
++
++Example: {{code language="none"}}ou="intern", dc="example", dc="com"{{/code}}
++
++== Make user data available to forms ==
++
++The LDAP user data for the currently authenticated user are stored in the JavaScript object {{code language="none"}}window.XFC_METADATA.user.rawData{{/code}} and can be accessed via JavaScript.
++
++{{info}}
++Which data the JSON structure contains under the rawData property depends mainly on the read rights of the LDAP account, which executes the user search in the LDAP system.
++{{/info}}
++
++To access the property ~/~/userPrincipalName~/~/ of the user from JavaScript, use the following code:
++
++{{code language="javascript"}}
++try {
++    // Auslesen der Property und Anzeige in einem Label
++    var elem = $('[name=txt1]');
++    var ldap = XFC_METADATA.user.rawData;
++    if(ldap.hasOwnProperty('userPrincipalName')) {
++        elem.html(ldap.userPrincipalName);
++    }
++} catch (err)  {}
++{{/code}}

Changes for page Einmalanmeldung

Summary

Details

Navigation