Here are some Frequently Asked Questions regarding Liferay Connected Services (LCS).
The following LCS features: Page Analytics, Snapshot Metrics, Fix Pack Management and Portal Properties have been discontinued. Please read the LCS Feature Deprecation Update to learn more about their removal.
- Our servers are behind a firewall and cannot communicate directly over the internet. Can I still use LCS?
- What security measures are offered by the LCS Platform?
- What is the authentication method and password policy for user accounts in LCS?
- What are the service conditions and restrictions that apply when we use LCS?
- How does LCS secure customer data?
- How can I restrict what information is sent to LCS?
- How do I connect to LCS from the service tier if my IT restricts connections?
- What happens when LCS is not reachable? Will the Liferay installation think it does not have an active registration?
Q: Our servers are behind a firewall and cannot communicate directly over the internet. Can I still use LCS?
- Customers can edit their firewall settings to allow traffic only to and from Public Hostnames and IP Addresses. Please see this KBase article for the latest up to date information on the necessary settings. LCS Preconfiguration.
- LCS is secured using industry best practices with appropriate firewalls and encryption. All communication to and from LCS is encrypted and conducted over HTTPS/SSL.
- Users can sign in with their Liferay.com account, the same that is used to access Liferay Help Center.
- See EULA available at lcs.liferay.com.
- LCS is hosted using industry standard best practices for maintaining firewalls and ensuring unauthorized access and login.
- LCS encrypts all data coming to and from LCS via SSL.
- All communications to the LCS servers on port 443 (HTTPS) and can be configured to use a proxy server, avoiding any additional customer firewall holes.
- LCS does not collect or store any sensitive customer data.
- All data stored in LCS is logically partitioned to ensure each customers’ data is segmented and cannot be retrieved by other customers accessing the system via the LCS dashboard and API mechanisms.
- LCS receives minimal information about connected servers, mainly the server's name and it's uptime status. This information is mandatory and cannot be restricted any further.
- Highly regulated IT environments (e.g. banks, insurance companies, defense contractors, etc) allow servers to communicate with external systems (e.g. LCS) using an authenticated proxy server. Your LCS connection can be configured to communicate via your IT's authenticated proxy servers over HTTPS. See Preconfiguring the LCS Client for more information.
Q: What happens when LCS is not reachable? Will the Liferay installation think it does not have an active registration?
- LCS is deployed on a global cloud infrastructure set up for automatic failure recovery. Thus, the potential for non-availability is quite low. However, in the event of a system outage, registered instances maintain a local copy of their uptime information to transmit back to LCS when LCS comes online. Active subscriptions also have a grace period of 30 days to re-establish connectivity to remain valid. This grace period is more than ample for LCS to come back online. Should an extended outage exist, Liferay support can provide temporary disconnected subscription keys to mitigate any potential impacts.
See the FAQ at the bottom of our Liferay Connected Services page.