FLS supports IPv4 (available from build #18692). The value should be a regular expression. The value should be a regular expression (available from build #17768).ĭefines the user's IP address. This parameter can't be configured in the same whitelist as LDAP integration.ĭefines the product build number. The value can be a plain hostname or a regular expression. This parameter can't be configured in the same whitelist as LDAP integration.ĭefines the user's host name. You can configure it into IDE by adding the user.name option to custom properties with the desirable userName. The value can be a plain username or a regular expression. So, do not use the symbol of the beginning of a string ( ^) and a symbol of the end ( $) of a string.ĭefines the user that launched an IDE. *.* regular expression during the preprocess, that's why the value will be compared to the whole string.
FLS converts the value of this parameter to the. The value can be a product name or a regular expression.
Parameters for rulesĭefines the product names to which this rule is applied. If you've modified the already-existing access-config.json file, you shouldn't restart FLS. Use the following parameters to configure the rules. Depending on type of the list, the triggered rule will either grant or reject a license for the received request. Each rule is a set of conditions that should all match to trigger the rule. The access-config.json file consists of one or several lists of rules: the whitelist, the blacklist, and the priority list.
To set user restrictions, create the access-config.json file and specify its path. This request is compared to the set of rules defined by the FLS administrator, and a license is either granted or rejected. When a user wants to obtain a license, the IDE sends a request to License Server. If you need to restrict someone's access to licenses, or you have prioritized users, who should get a license even if there are none available, the FLS administrator can configure user restrictions. New License Vault available! See the License Vault documentation for more details.
0 kommentar(er)
