Single Sign-On for the VIP Dashboard
Single Sign-On (SSO) for logging in to the VIP Dashboard can be configured for an organization as an optional—or enforced—authentication method.
Ready to get started with WordPress VIP? Contact us
Showing page 5 of 26
Single Sign-On (SSO) for logging in to the VIP Dashboard can be configured for an organization as an optional—or enforced—authentication method.
The WordPress VIP Block Governance plugin provides the ability to limit the types of Gutenberg blocks that can be added to the block editor and the styles that can be applied to them. The rules applied for block and style options can also be defined by specific post types and/or user roles.
An environment indicator label will display by default on local development environments, and can be selectively enabled for non-production VIP Platform environments.
A generated custom TLS certificate must meet all of the following requirements in order to be successfully installed:
By default a GitHub repository within the wpcomvip GitHub organization is created for every application and a branch is configured to deploy code to each of its environments. By default, application code is developed in an application’s provided wpcomvip GitHub repository and deployed via the Default Deployment method.
Each of an application’s VIP Platform environments can track its own specific branch of the application’s wpcomvip GitHub repository.
Drop-ins are files designed to replace, add, or enhance specific WordPress Core features.
Logs can also be useful for debugging, security, and incident investigation.
The WordPress VIP Platform provides a resilient infrastructure that includes full page cache, object cache, database indexes, database read replicas, separate handling of static files, dynamic image size transformation, and auto-scaling of web containers.
Penetration tests, security assessments, or other scans can be run by a customer against their application’s WordPress VIP Platform environments.