Domino web security and authentication
HCL Domino web security, authentication and CertMgr services
Strengthen Domino web applications and infrastructure with practical support for OIDC, identity-provider integration, TLS certificate lifecycle management and controlled security change.
Why it matters
Common challenges we help solve
Authentication, TLS and certificate handling may have grown around older operating models or manual processes.
Security improvements need to be planned around real users, applications, clients and integrations.
Teams need clear priorities for OIDC, CertMgr, TLS, identity and upgrade readiness.
Approach
How Domino People helps
- Assess current authentication, certificate, TLS, client and server security posture.
- Plan practical OIDC, CertMgr and identity integration steps around the existing environment.
- Implement controlled changes with testing, rollback thinking and support documentation.
What we can do
Specialist work shaped around the outcome you need
Security work around Domino is easier to manage when it is connected to the way people actually sign in, access applications, renew certificates and support services. We help turn a collection of technical tasks into a prioritised plan that protects users and reduces operational surprises.
Reviews of Domino authentication, TLS, certificates, client access and identity-provider dependencies.
OIDC and identity integration planning that considers user groups, existing clients, applications, testing and change communication.
CertMgr, ACME and certificate lifecycle improvements covering ownership, renewal, monitoring, documentation and service continuity, including Let’s Encrypt where appropriate.
Web authentication design for OIDC, a single identity provider and MFA patterns such as TOTP or passkeys, subject to the selected identity provider and Domino architecture.
TLS renewal readiness that prepares teams for shorter public TLS certificate lifetimes, with testing, runbooks and monitoring.
Controlled security implementation support with checkpoints, rollback thinking and evidence for internal stakeholders.
How we can start
We can begin with the area that causes the most concern—an upcoming certificate change, an authentication project, an upgrade dependency or a wider security review. The first outcome is a clear, sequenced plan rather than a vague list of technical recommendations.
Discuss your requirement with Domino PeopleOutcomes
Practical outcomes, not generic transformation talk
Domino People focuses on useful, supportable improvements that fit how your Domino environment is actually used.
- A clearer security roadmap for your current Domino estate.
- More maintainable certificate and authentication patterns.
- Reduced operational risk through planned, tested and documented security improvements.
Related Domino People services
Explore related support
FAQ
Questions teams often ask
Can you help us assess OIDC readiness?
Yes. Domino People can review your current authentication model, user groups, clients, servers and identity provider requirements before implementation.
Is CertMgr only a technical certificate task?
No. Certificate management also affects operations, renewals, ownership, monitoring and service continuity.
Can security changes be phased?
Yes. A phased plan helps reduce risk by sequencing assessment, testing, communication, rollout and rollback considerations.
How do you reduce risk when changing authentication or certificates?
We identify the people, clients, applications, servers and integrations affected before making a change. A controlled plan includes test cases, communications, timing, ownership and rollback considerations. That approach reduces the chance that a technically correct change creates an avoidable service interruption.
Can CertMgr and ACME reduce certificate-renewal effort?
They can reduce manual effort when the Domino version, certificate authority and deployment architecture are suitable. We assess the certificate inventory, ACME options, validation path, ownership and monitoring before recommending an automated renewal approach, including Let’s Encrypt where appropriate.
Can we use TOTP or passkeys for Domino web applications?
The right approach depends on the Domino release, the application access pattern and the chosen identity provider. We can design an OIDC-based model that considers MFA options such as TOTP or passkeys, then test it with the affected users, browsers and applications before rollout.
How should we prepare for shorter public TLS certificate lifetimes?
Shorter renewal cycles make certificate ownership, inventory, automation, monitoring and tested renewal runbooks more important. We help teams identify dependencies and make renewals repeatable rather than relying on an urgent manual change.
Next step
Need practical HCL Domino help?
Tell us what you are trying to improve and we will help you choose a controlled path forward.
Contact Domino People