Securing ServicePulse

Authentication

ServicePulse authentication is configured in ServiceControl, not in ServicePulse itself. When authentication is enabled on ServiceControl, ServicePulse automatically retrieves the OIDC configuration from the primary ServiceControl instance and presents users with a sign-in page.

To set up authentication, follow the ServiceControl security guide.

When role-based access control is enabled in ServiceControl, ServicePulse hides or disables the tabs, pages, and buttons that the signed-in user is not permitted to use.

Enable HTTPS on ServicePulse

ServicePulse should be served over HTTPS to protect user sessions and tokens in transit. Configure a TLS certificate so ServicePulse serves HTTPS directly.

See TLS configuration for certificate options and configuration examples.

Advanced deployment patterns

For deployments that use a reverse proxy for TLS termination, or require end-to-end encryption between a proxy and ServicePulse, see the hosting guide.

Reference

• Authentication configuration
• Role-based access control
• TLS configuration
• Forward headers for reverse proxy
• Hosting guide
• ServiceControl security