Portals for public bodies: accessible, with Cl@ve and with the security you are asked for.
Who it is for
For ministries, public agencies, regional governments, local authorities and publicly owned companies with a portal, an e-services site or an intranet to build, migrate or maintain.
The problem
The portal has to be accessible and the accessibility statement has not been reviewed in years. Citizens have to sign in with Cl@ve and the integration never quite works. The tender asks for security requirements the supplier cannot explain. And the contract ends, and whoever knew the portal leaves with it.
How we solve it
We build, migrate and maintain portals for public bodies, with what a public body needs from day one. Accessibility is designed in, not patched on at the end. We have integrated sign-in with Cl@ve into Liferay and it is in production. And we work to the security requirements your organization sets, throughout the life of the project.
What it includes
Accessibility
Design with the EN 301 549 standard as the starting point and a report from the official validator of Spain's Observatorio de Accesibilidad Web.
Sign-in with Cl@ve
Access with the electronic ID card, a digital certificate and Cl@ve PIN, with Cl@ve as the portal's identity provider.
National Security Framework (ENS)
We work with the controls of the Spanish National Security Framework and with the requirements your organization sets.
Portals, e-services sites and intranets
New projects on Liferay and evolution of the ones you already have, with search for large catalogs.
Migration and maintenance
Upgrades from unsupported versions and maintenance with response times in writing.
Orderly handover
Code in your repositories, environments, automated deployments and technical documentation.
How we work
We work in short deliveries your team can see and validate in a test environment. Your organization approves the go-live. Every delivery carries its automated tests and up-to-date documentation. If another team runs the portal when the contract ends, it has what it needs to carry on.
Cases
- See the case study: Integración de sistema Cl@ve en Liferay
- See the case study: Portal web del INSST
- See the case study: Centro de Investigaciones Sociológicas (CIS)
- See the case study: Confederación Hidrográfica del Cantábrico
- See the case study: Consejería de Derechos Sociales y Bienestar del Principado de Asturias
How it is built
On Liferay DXP and Liferay CE, with React client extensions for what is new and the existing modules maintained. Cl@ve is configured as the portal's identity provider, so citizens sign in with the electronic ID card, a digital certificate or Cl@ve PIN.
Interfaces are designed with the EN 301 549 standard as the starting point. The accessibility report uses the official validator of Spain's Observatorio de Accesibilidad Web and can include a manual review for the accessibility statement. A report measures the state; on its own it does not guarantee compliance.
On security we work with the controls of the Spanish National Security Framework (ENS) and are in the process of being audited. On every project: secrets centralized outside the code, static analysis with our own rules for Liferay, dependencies reviewed and auditable CI/CD deployments, across environments and with rollback.
No change reaches production without going through four review agents (security, accessibility, quality and functionality) and a person. The quality gate is the one on all our projects: a minimum of 80 % test coverage and 0 open issues in SonarQube.
Frequently asked questions
Do you work with public administrations?
Yes. We design with the EN 301 549 standard as the starting point and work to the security and Cl@ve integration requirements the organization sets, throughout the life of the project.
Have you integrated Cl@ve into Liferay?
Yes. We configured Cl@ve as the portal's identity provider, with access through the electronic ID card, a digital certificate and Cl@ve PIN. It is among the published case studies.
What does working with the controls of the National Security Framework mean?
That we apply its measures in the way we work and are in the process of being audited. We do not present it as a certification.
Does the accessibility report guarantee the portal is accessible?
No. A report measures the state. Accessibility is achieved by designing and fixing, and kept by reviewing every change. The report can include a manual review for the accessibility statement.
What happens to the portal when the contract ends?
The code stays in your repositories, with the environments, the automated deployments and the technical documentation. Whoever comes next can carry on from there.
Also in Portals and development
Liferay migration
From an unsupported version to a current one, with a rehearsal and a rollback.
Liferay maintenance
Patches, incidents, changes and versions, with the same team.
Liferay consulting
Architecture, performance and integrations, to decide with data.
Liferay audit
The real state of the portal, with the risks in priority order.
Liferay training
Tailored Liferay courses for teams, on their own portal.
The next step
Tell us how you work today and we will tell you where to start.