|
@@ -267,8 +267,8 @@ Setting_Description_challenge.showConfirmation=Enable this option to show the re
|
|
Setting_Description_challenge.token.sendMethod=Select the methods you want to use for sending the token code or new password to the user.
|
|
Setting_Description_challenge.token.sendMethod=Select the methods you want to use for sending the token code or new password to the user.
|
|
Setting_Description_challenge.userAttribute=Specify the attribute to use for response storage when storing responses in an LDAP directory.
|
|
Setting_Description_challenge.userAttribute=Specify the attribute to use for response storage when storing responses in an LDAP directory.
|
|
Setting_Description_changePassword.writeAttributes=Add actions to take after a user change password event occurs. @PwmAppName@ invokes these actions just after writing the password. You can use macros within the action and are expanded based on the logged in user.
|
|
Setting_Description_changePassword.writeAttributes=Add actions to take after a user change password event occurs. @PwmAppName@ invokes these actions just after writing the password. You can use macros within the action and are expanded based on the logged in user.
|
|
-Setting_Description_cluster.enable=Enable cluster module.
|
|
|
|
-Setting_Description_cluster.storageMode=Data storage system used for cluster module. <p>If <b>LDAP</b> is selected, a test user (<a data-gotoSettingLink\="ldap.testuser.username">@PwmSettingReference\:ldap.testuser.username@</a>) must be configured and the response storage attribute (<a data-gotoSettingLink\="ldap.testuser.username">@PwmSettingReference\:ldap.testuser.username@</a>) must be writable by the proxy user.</p><p>If <b>DATABASE</b> is selected then a database must be configured and available for @PwmAppName@ to operate.</p>
|
|
|
|
|
|
+Setting_Description_nodeService.enable=Enable or Disable the node service. The node service allows @PwmAppName@ to detect and identify when multiple application nodes are similar configured and can share user sessions.
|
|
|
|
+Setting_Description_nodeService.storageMode=Data storage system used for node service. <p>If <b>LDAP</b> is selected, a test user (<a data-gotoSettingLink\="ldap.testuser.username">@PwmSettingReference\:ldap.testuser.username@</a>) must be configured and the response storage attribute (<a data-gotoSettingLink\="ldap.testuser.username">@PwmSettingReference\:ldap.testuser.username@</a>) must be writable by the proxy user.</p><p>If <b>DATABASE</b> is selected then a database must be configured and available for @PwmAppName@ to operate.</p>
|
|
Setting_Description_command.checkResponses.queryMatch=Controls which users are forced to setup responses. Users that match this permission will be forced to setup responses.
|
|
Setting_Description_command.checkResponses.queryMatch=Controls which users are forced to setup responses. Users that match this permission will be forced to setup responses.
|
|
Setting_Description_db.classname=Add the remote database JDBC driver class name. Consult the database vendor to determine the correct class name for your database.<br/><br/><table><tr><td class\="key">Database Type</td><td class\="key">Example Class Name</td></tr><tr><td>MS-SQL</td><td>com.microsoft.sqlserver.jdbc.SQLServerDriver</td></tr><tr><td>MS-SQL using jTDS</td><td>net.sourceforge.jtds.jdbc.Driver</td></tr><tr><td>Oracle</td><td>oracle.jdbc.OracleDriver</td></tr></table><div class="footnote">The above are examples only, consult your database documentation for the proper setting value.</div>
|
|
Setting_Description_db.classname=Add the remote database JDBC driver class name. Consult the database vendor to determine the correct class name for your database.<br/><br/><table><tr><td class\="key">Database Type</td><td class\="key">Example Class Name</td></tr><tr><td>MS-SQL</td><td>com.microsoft.sqlserver.jdbc.SQLServerDriver</td></tr><tr><td>MS-SQL using jTDS</td><td>net.sourceforge.jtds.jdbc.Driver</td></tr><tr><td>Oracle</td><td>oracle.jdbc.OracleDriver</td></tr></table><div class="footnote">The above are examples only, consult your database documentation for the proper setting value.</div>
|
|
Setting_Description_db.columnType.key=Specify the database column type for key columns. @PwmAppName@ uses the column type only during schema creation. All tables are two columns: a key and a value column. For most databases the standard VARCHAR column format is appropriate for the key column. Data stored in the key column generally is US-ASCII keys.
|
|
Setting_Description_db.columnType.key=Specify the database column type for key columns. @PwmAppName@ uses the column type only during schema creation. All tables are two columns: a key and a value column. For most databases the standard VARCHAR column format is appropriate for the key column. Data stored in the key column generally is US-ASCII keys.
|
|
@@ -476,7 +476,7 @@ Setting_Description_ldap.serverCerts=Import the LDAP Server Certificates. @PwmA
|
|
Setting_Description_ldap.serverUrls=Add a list of LDAP servers in URL format that @PwmAppName@ uses for a fail-over configuration. @PwmAppName@ uses the servers in order of appearance in this list. If the first server is unavailable @PwmAppName@ uses the next available server in the list. @PwmAppName@ periodically checks the first server to see if it has become available.<ul><li>For secure SSL, use the "<i>ldaps\://servername\:636</i>" format</li><li>For plain-text servers, use "<i>ldap\://serverame\:389</i>" format (not recommended)</li></ul><p>When using secure connections, the Java virtual machine must trust the directory server, either because you have manually added the public key certificate from the tree to the Java keystore or you imported the certificate into the setting <i>LDAP Server Certificates</i>.<ul><li>Do not use a non-secure connection for anything but the most basic testing purposes (Many LDAP servers reject password operations on non-secure connections)</li><li>Do not use a load-balancing device for LDAP high availability, instead use the built in LDAP server fail-over functionality</li><li>Do not use a DNS round-robin address</li><li>Avoid using the network address, use the proper fully-qualified domain name address for the server</li></ul>
|
|
Setting_Description_ldap.serverUrls=Add a list of LDAP servers in URL format that @PwmAppName@ uses for a fail-over configuration. @PwmAppName@ uses the servers in order of appearance in this list. If the first server is unavailable @PwmAppName@ uses the next available server in the list. @PwmAppName@ periodically checks the first server to see if it has become available.<ul><li>For secure SSL, use the "<i>ldaps\://servername\:636</i>" format</li><li>For plain-text servers, use "<i>ldap\://serverame\:389</i>" format (not recommended)</li></ul><p>When using secure connections, the Java virtual machine must trust the directory server, either because you have manually added the public key certificate from the tree to the Java keystore or you imported the certificate into the setting <i>LDAP Server Certificates</i>.<ul><li>Do not use a non-secure connection for anything but the most basic testing purposes (Many LDAP servers reject password operations on non-secure connections)</li><li>Do not use a load-balancing device for LDAP high availability, instead use the built in LDAP server fail-over functionality</li><li>Do not use a DNS round-robin address</li><li>Avoid using the network address, use the proper fully-qualified domain name address for the server</li></ul>
|
|
Setting_Description_ldap.testuser.username=Specify the fully qualified DN of an LDAP test user that @PwmAppName@ uses to test functionality and for access to the LDAP directory. Configure this user similar to a normal user account with normal access privileges. @PwmAppName@ periodically uses this account to perform a health check, including changing the password of the account. <br/><br/><b>Using a test user account greatly increases the system's ability to detect and alert configuration and health issues.</b><br/><br/>@PwmAppName@ tests the following functionality (if enabled) using the test user account.<ul><li>Authentication</li><li>Password policy reading</li><li>Set password</li><li>Set Challenge/Responses</li><li>Load Challenge/Responses</li></ul>
|
|
Setting_Description_ldap.testuser.username=Specify the fully qualified DN of an LDAP test user that @PwmAppName@ uses to test functionality and for access to the LDAP directory. Configure this user similar to a normal user account with normal access privileges. @PwmAppName@ periodically uses this account to perform a health check, including changing the password of the account. <br/><br/><b>Using a test user account greatly increases the system's ability to detect and alert configuration and health issues.</b><br/><br/>@PwmAppName@ tests the following functionality (if enabled) using the test user account.<ul><li>Authentication</li><li>Password policy reading</li><li>Set password</li><li>Set Challenge/Responses</li><li>Load Challenge/Responses</li></ul>
|
|
Setting_Description_ldap.user.group.attribute=Specify an attribute on the user entry that references group entries. The value of this attribute in the directory must be a LDAP DN.
|
|
Setting_Description_ldap.user.group.attribute=Specify an attribute on the user entry that references group entries. The value of this attribute in the directory must be a LDAP DN.
|
|
-Setting_Description_ldap.user.pwNotify.attribute=Specify an attribute that is used by @PwmAppName@ to store data for the password expiration notification service.
|
|
|
|
|
|
+Setting_Description_ldap.user.appData.attribute=Specify an attribute that is used by @PwmAppName@ to store data for the various application data including ldap node services and password password expiration notification service.
|
|
Setting_Description_ldap.user.language.attribute=Attribute that contains the language of the user in RFC1766 format. (The same format used by web browsers and the HTTP Accept-Language header.) This value is used only for user interactions when the user does not have an active web session such as an email notification.
|
|
Setting_Description_ldap.user.language.attribute=Attribute that contains the language of the user in RFC1766 format. (The same format used by web browsers and the HTTP Accept-Language header.) This value is used only for user interactions when the user does not have an active web session such as an email notification.
|
|
Setting_Description_ldap.user.language.autoSet=When enabled, the user's effective locale for a web session will be written to the LDAP language attribute.
|
|
Setting_Description_ldap.user.language.autoSet=When enabled, the user's effective locale for a web session will be written to the LDAP language attribute.
|
|
Setting_Description_ldap.username.attr=Specify the attribute @PwmAppName@ uses for the user name. If blank, @PwmAppName@ uses the LDAP Naming Attribute. This option allows fields that display or store the <b>User Name</b> or <b>User ID</b> of a user to show something other then the LDAP Naming Attribute if appropriate. This value must be unique for this system.
|
|
Setting_Description_ldap.username.attr=Specify the attribute @PwmAppName@ uses for the user name. If blank, @PwmAppName@ uses the LDAP Naming Attribute. This option allows fields that display or store the <b>User Name</b> or <b>User ID</b> of a user to show something other then the LDAP Naming Attribute if appropriate. This value must be unique for this system.
|
|
@@ -621,8 +621,8 @@ Setting_Description_pwm.securityKey=<p>Specify a Security Key used for cryptogra
|
|
Setting_Description_pwm.seedlist.location=Specify the location of the seed list in the form of a valid URL. When @PwmAppName@ randomly generates passwords, it can generate a "friendly", random password suggestions to users. It does this by using a "seed" word or words, and then modifying that word randomly until it is sufficiently complex and meets the configured rules computed for the user.<br/><br/>The value must be a valid URL, using the protocol "file" (local file system), "http", or "https".
|
|
Setting_Description_pwm.seedlist.location=Specify the location of the seed list in the form of a valid URL. When @PwmAppName@ randomly generates passwords, it can generate a "friendly", random password suggestions to users. It does this by using a "seed" word or words, and then modifying that word randomly until it is sufficiently complex and meets the configured rules computed for the user.<br/><br/>The value must be a valid URL, using the protocol "file" (local file system), "http", or "https".
|
|
Setting_Description_pwm.selfURL=<p>The URL to this application, as seen by users. @PwmAppName@ uses the value in email macros and other user-facing communications.</p><p>The URL must use a valid fully qualified hostname. Do not use a network address.</p><p>In simple environments, the URL will be the base of the URL in the browser you are currently using to view this page, however in more complex environments the URL will typically be an upstream proxy, gateway or network device.</p><p>The URL should include the path to the base application, typically <code>/@Case:lower:[[@PwmAppName@]]@</code>.</p>
|
|
Setting_Description_pwm.selfURL=<p>The URL to this application, as seen by users. @PwmAppName@ uses the value in email macros and other user-facing communications.</p><p>The URL must use a valid fully qualified hostname. Do not use a network address.</p><p>In simple environments, the URL will be the base of the URL in the browser you are currently using to view this page, however in more complex environments the URL will typically be an upstream proxy, gateway or network device.</p><p>The URL should include the path to the base application, typically <code>/@Case:lower:[[@PwmAppName@]]@</code>.</p>
|
|
Setting_Description_pwm.wordlist.location=Specify a word list file URL for dictionary checking to prevent users from using commonly used words as passwords. Using word lists is an important part of password security. Word lists are used by intruders to guess common passwords. The default word list included contains commonly used English passwords. <br/><br/>The first time a startup occurs with a new word list setting, it takes some time to compile the word list into a database. See the status screen and logs for progress information. The word list file format is one or more text files containing a single word per line, enclosed in a ZIP file. The String <i>\!\#comment\:</i> at the beginning of a line indicates a comment. <br/><br/>The value must be a valid URL, using the protocol "file" (local file system), "http", or "https".
|
|
Setting_Description_pwm.wordlist.location=Specify a word list file URL for dictionary checking to prevent users from using commonly used words as passwords. Using word lists is an important part of password security. Word lists are used by intruders to guess common passwords. The default word list included contains commonly used English passwords. <br/><br/>The first time a startup occurs with a new word list setting, it takes some time to compile the word list into a database. See the status screen and logs for progress information. The word list file format is one or more text files containing a single word per line, enclosed in a ZIP file. The String <i>\!\#comment\:</i> at the beginning of a line indicates a comment. <br/><br/>The value must be a valid URL, using the protocol "file" (local file system), "http", or "https".
|
|
-Setting_Description_pwNotify.storageMode=Select storage mode used by cluster module.
|
|
|
|
-Setting_Description_pwNotify.enable=<p>Enable password expiration notification service. Operation of this service requires that a remote database be configured. Status of this service can be viewed on the <code>Administration -> Dashboard -> Password Notification</code> page. The service will nominally execute once per day on the cluster master server.</p><p>If a job is missed because of an @PwmAppName@, LDAP, or database service interuption it will be run within the next 24 hours as soon as service is restored. Running a job more than once will not result in duplicate emails sent to the user.</p>
|
|
|
|
|
|
+Setting_Description_pwNotify.storageMode=Select storage mode used by node service module.
|
|
|
|
+Setting_Description_pwNotify.enable=<p>Enable password expiration notification service. Operation of this service requires that a node service be configured. Status of this service can be viewed on the <code>Administration -> Dashboard -> Password Notification</code> page. The service will nominally execute once per day on the master node server.</p><p>If a job is missed because of an @PwmAppName@, LDAP, or database service interruption it will be run within the next 24 hours as soon as service is restored. Running a job more than once will not result in duplicate emails sent to the user.</p><p>If a user's password expiration time changes since the last job, a new notification will be sent as appropriate.</p>
|
|
Setting_Description_pwNotify.queryString=Users that will receive password expiration notifications.
|
|
Setting_Description_pwNotify.queryString=Users that will receive password expiration notifications.
|
|
Setting_Description_pwNotify.intervals=Expiration Notification Day Intervals. The number of days before a user's password expiration before which an email notice will be set.
|
|
Setting_Description_pwNotify.intervals=Expiration Notification Day Intervals. The number of days before a user's password expiration before which an email notice will be set.
|
|
Setting_Description_pwNotify.job.offSet=GMT job offset time. The expiration notice job will normally be executed at 0:00 GMT. This value can be adjusted to change the standard time of day the job is run.
|
|
Setting_Description_pwNotify.job.offSet=GMT job offset time. The expiration notice job will normally be executed at 0:00 GMT. This value can be adjusted to change the standard time of day the job is run.
|
|
@@ -784,8 +784,8 @@ Setting_Label_challenge.showConfirmation=Show Response Confirmation
|
|
Setting_Label_challenge.token.sendMethod=Token Send Method
|
|
Setting_Label_challenge.token.sendMethod=Token Send Method
|
|
Setting_Label_challenge.userAttribute=Response Storage Attribute
|
|
Setting_Label_challenge.userAttribute=Response Storage Attribute
|
|
Setting_Label_changePassword.writeAttributes=Post Password Change Actions
|
|
Setting_Label_changePassword.writeAttributes=Post Password Change Actions
|
|
-Setting_Label_cluster.enable=Cluster Enabled
|
|
|
|
-Setting_Label_cluster.storageMode=Cluster Mode
|
|
|
|
|
|
+Setting_Label_nodeService.enable=Node Service Enabled
|
|
|
|
+Setting_Label_nodeService.storageMode=Node Service Storage Mode
|
|
Setting_Label_command.checkResponses.queryMatch=Check Responses Match
|
|
Setting_Label_command.checkResponses.queryMatch=Check Responses Match
|
|
Setting_Label_db.classname=Database Class
|
|
Setting_Label_db.classname=Database Class
|
|
Setting_Label_db.columnType.key=Database Key Column Type
|
|
Setting_Label_db.columnType.key=Database Key Column Type
|
|
@@ -993,7 +993,7 @@ Setting_Label_ldap.serverCerts=LDAP Certificates
|
|
Setting_Label_ldap.serverUrls=LDAP URLs
|
|
Setting_Label_ldap.serverUrls=LDAP URLs
|
|
Setting_Label_ldap.testuser.username=LDAP Test User
|
|
Setting_Label_ldap.testuser.username=LDAP Test User
|
|
Setting_Label_ldap.user.group.attribute=User Group Attribute
|
|
Setting_Label_ldap.user.group.attribute=User Group Attribute
|
|
-Setting_Label_ldap.user.pwNotify.attribute=Password Notify Service Attribute
|
|
|
|
|
|
+Setting_Label_ldap.user.appData.attribute=Application Data Attribute
|
|
Setting_Label_ldap.user.language.attribute=User Language Attribute
|
|
Setting_Label_ldap.user.language.attribute=User Language Attribute
|
|
Setting_Label_ldap.user.language.autoSet=Auto Set User Language Attribute
|
|
Setting_Label_ldap.user.language.autoSet=Auto Set User Language Attribute
|
|
Setting_Label_ldap.username.attr=Attribute to use for User Name
|
|
Setting_Label_ldap.username.attr=Attribute to use for User Name
|