Elaboración de Cuestionario

Set the following encryption algorithm to encrypt passwords. The default al- gorithm is SHA (SHA-1). If set to NONE, passwords are stored in the database as plain text. The SHA-512 algorithm is currently unsupported.

Examples: passwords.encryption.algorithm=CRYPT passwords.encryption.algorithm=MD2 passwords.encryption.algorithm=MD5 passwords.encryption.algorithm=NONE passwords.encryption.algorithm=SHA passwords.encryption.algorithm=SHA-256 passwords.encryption.algorithm=SHA-384 passwords.encryption.algorithm=SSHA

Digested passwords are encoded via base64 or hex encoding. The default is base64.

passwords.digest.encoding=base64 #passwords.digest.encoding=hex

Input a class name that extends com.liferay.portal.security.pwd.BasicToolkit. This class will be called to generate and validate passwords.

Examples:

passwords.toolkit=com.liferay.portal.security.pwd.PasswordPolicyToolkit passwords.toolkit=com.liferay.portal.security.pwd.RegExpToolkit

If you choose to use com.liferay.portal.security.pwd.PasswordPolicyToolkit as your password toolkit, you can choose either static or dynamic password generation. Static is set through the property passwords.passwordpolicytoolkit.static and dynamic uses the class com.liferay.util.PwdGenerator to generate the password. If you are using LDAP password syntax checking, you will also have to use the static generator so that you can guarantee that passwords obey its rules.

Examples:

passwords.passwordpolicytoolkit.generator=static passwords.passwordpolicytoolkit.generator=dynamic passwords.passwordpolicytoolkit.static=iheartliferay

If you choose to use com.liferay.portal.security.pwd.RegExpToolkit as your password toolkit, set the regular expression pattern that will be used to generate and validate passwords.

Note that \ is replaced with \\ to work in Java.

The first pattern ensures that passwords must have at least 4 valid characters consisting of digits or letters.

The second pattern ensures that passwords must have at least 8 valid characters consisting of digits or letters.

Examples:

passwords.regexptoolkit.pattern=(?=.{4})(?:[a-zA-Z0-9]*) passwords.regexptoolkit.pattern=(?=.{8})(?:[a-zA-Z0-9]*)

Set the length and key for generating passwords.

Examples: passwords.regexptoolkit.charset=0123456789 passwords.regexptoolkit.charset=0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcde- fghijklmnopqrstuvwxyz Examples: passwords.regexptoolkit.length=4 passwords.regexptoolkit.length=8

Set the name of the default password policy.

passwords.default.policy.name=Default Password Policy

P

Set the default permission checker class used by com.liferay.portal.security.permis-

sion.PermissionCheckerFactory to check permissions for actions on objects. This class

can be overridden with a custom class that extends com.liferay.portal.security.permis-

sion.PermissionCheckerImpl.

permissions.checker=com.liferay.portal.security.permission.PermissionCheck- erImpl

Set the algorithm used to check permissions for a user. This is useful so that you can optimize the search for different databases. See com.liferay.portal.service.impl.Per-

missionLocalServiceImpl. The default is method two.

The first algorithm uses several if statements to query the database for these five things in order. If it finds any one of them, it returns true:

● Is the user connected to one of the permissions via group or organization roles?

● Is the user associated with groups or organizations that are directly connected to one of the permissions?

● Is the user connected to one of the permissions via user roles? ● Is the user connected to one of the permissions via user group roles? ● Is the user directly connected to one of the permissions?

permissions.user.check.algorithm=1

The second algorithm (the default) does a database join and checks the permis- sions in one step, by calling countByGroupsRoles, countByGroupsPermissions, countByUser-

sRoles, countByUserGroupRole, and countByUsersPermissions in one method.

permissions.user.check.algorithm=2

bines the role check into one step. If it finds any of the following items, it returns true: ● Is the user associated with groups or organizations that are directly connec-

ted to one of the permissions?

● Is the user associated with a role that is directly connected to one of the per- missions?

● Is the user directly connected to one of the permissions? permissions.user.check.algorithm=3

The fourth algorithm does a database join and checks the permissions that al- gorithm three checks in one step, by calling countByGroupsPermissions, countByRole-

sPermissions, and countByUsersPermissions in one method.

permissions.user.check.algorithm=4

Set the default permissions list filter class. This class must implement com.liferay.-

portal.kernel.security.permission.PermissionsListFilter. This is used if you want to filter the

list of permissions before it is actually persisted. For example, if you want to make sure that all users who create objects never have the UPDATE action, then you can fil- ter that list and remove any permissions that have the UPDATE action before it is per- sisted.

permissions.list.filter=com.liferay.portal.security.permission.Permis- sionsListFilterImpl

C

Set the maximum number of captcha checks per portlet session. Set this value to 0 to always check. Set this value to a number less than 0 to never check. Unauthentic- ated users will always be checked on every request if captcha checks is enabled.

captcha.max.challenges=1

Set whether or not to use captcha checks for the following actions. captcha.check.portal.create_account=true

captcha.check.portal.send_password=true

captcha.check.portlet.message_boards.edit_category=false captcha.check.portlet.message_boards.edit_message=false