Authentication towards the Spotfire database
This authentication method requires the Spotfire user directory to be configured as Spotfire database.
When the user directory is set to Database, the administrator usually enters the user names and passwords into the Spotfire database manually. The names and passwords can be imported from a CSV file, or automatically created as new users log in to the server. The option to create users automatically is available through the post-authentication filter.
The basic Spotfire database configuration for user and password supports modern standards and recommendations for restricting password minimum and maximum lengths. You can set minimum and maximum password length policy properties for user credentials stored in the Spotfire database using one of the following two methods:
- Using the CLI command
set-config-prop
. - Using the XML View of the configuration tool.
Configuration setting | Description |
---|---|
security.password-policies.password-length-policy.enabled
|
Enable the password length policy option. |
security.password-policies.password-length-policy.minimum-password-length
|
Set the minimum option for password length. |
security.password-policies.password-length-policy.maximum-password-length
|
Set the maximum option for password length. |
Examples
config set-config-prop --name="security.password-policies.password-length-policy.enabled" --value="true"
config set-config-prop --name="security.password-policies.password-length-policy.minimum-password-length" --value="5"
config set-config-prop --name="security.password-policies.password-length-policy.maximum-password-length" --value="10"
Alternatively, from the XML View of the configuration tool, edit the Spotfire Server configuration for minimum and maximum password length.
Example
<security>
.....
<password-policies>
<password-length-policy>
<enabled>true</enabled>
<minimum-password-length>5</minimum-password-length>
<maximum-password-length>10</maximum-password-length>
</password-length-policy>
</password-policies>
</security>
For more information, see the following.