This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. Liferay Users and Screennames
The screenname validation process has two different parts when a screenname is created, for instance on new users, or imported users (from an LDAP):
1. External Validation
Liferay accepts a custom validation class defined using the Hook mechanism. This consists in overriding the following property at portal-ext.properties:
users.screen.name.validator=com.liferay.portal.security.auth.DefaultScreenNameValidator
2. Internal Validation
Once the external validation has been passed, there are some checks that Liferay implements internally to be consistent.
3. How it works
The following workflow explains how Liferay checks if the screenname is valid or not.
22175 Visualizações
