Certificates and protected browser data
Powerfront manages the certificates and protection material used for secure connections and remembered browser verification.
What it is
INSIDE uses certificates for configured HTTPS connections and some connected-service authentication. It also protects browser-held verification information before saving it in a cookie. Powerfront manages the hosting certificates and protection material for these functions.
Who uses it and why
Administrators coordinate certificate-related changes with Powerfront and their identity or email teams. Developers need to know which connection or integration is affected when a certificate changes. Operators normally use the resulting sign-in experience without handling this material themselves.
Where to find it
Hosting certificates and browser-data protection have no client Settings screen. Ask Powerfront to review them.
Powerfront manages federation certificates under Settings › Account › Single Sign-On. Powerfront manages certificate-based email authentication separately through Settings › Email › Email Accounts.
How it works
For a configured HTTPS connection, INSIDE loads the certificate assigned to the service address. Hosting arrangements can use certificates selected for different service names or listening ports.
When you choose to remember a verified browser, INSIDE protects the saved browser information and checks it when reading it later. The associated remembered-browser token must also remain valid. If the protected information cannot be read, it does not restore remembered verification, so a fresh verification may be needed.
SAML certificates and certificate-based email credentials belong to their respective integrations. Changing one does not automatically update the others.
Configure it
Ask Powerfront to coordinate changes to hosting certificates or browser-data protection. For federation or email authentication, identify the affected integration and arrange the certificate change with Powerfront and the team responsible for that service.
There is no client control here for a universal certificate lifetime, automatic renewal schedule or protection-key rotation interval. Ask Powerfront to confirm the arrangements that apply to your deployment.
Limits and good to know
- Remembered-browser verification depends on both valid browser information and its account token. Clearing cookies or invalidating the token can require verification again.
- A certificate for HTTPS, a SAML certificate and an email authentication certificate serve different purposes.
- Certificate support does not establish an automatic renewal or expiry-notification service for every certificate.
- HTTPS protects the connection. It does not establish encryption of every stored record or exported file.
Depends on and works with
View all connections as a list
This feature uses
- Email account and mailbox setupConfigured by
Email Accounts holds certificate-based mailbox credentials and their recorded expiry separately from hosting certificates.
- Logout and remembered computersRelated
Remembered-computer verification needs readable protected browser data and a valid remembered token.
- Single sign-on with SAML 2.0Configured by
SAML federation has its own certificate configuration managed by Powerfront.
FAQ and troubleshooting
Who changes a hosting certificate?
Powerfront manages this change. Identify the affected service address and coordinate the required certificate update with Powerfront.
Why did INSIDE ask for verification again on a remembered browser?
Its saved verification may no longer be readable or valid, its token may have expired, or browser cookies may have been cleared. Complete verification again and ask Powerfront to investigate repeated prompts.
Does changing our SAML certificate change HTTPS too?
No. Federation and HTTPS have separate certificate arrangements.
Will INSIDE automatically renew our certificate?
Do not assume that from this feature. Ask Powerfront to confirm renewal ownership and the process for the affected certificate.