If your JWT token is compromised, you should reset your shared secret and revoke all existing tokens.
Resetting the shared secret will invalidate the access of anyone who had previously authenticated, preventing them from viewing restricted content until a new valid token is issued. This ensures that your restricted content remains secure and only accessible to authorized users.
To show restricted help center content in Web Widget (Classic), you need to configure your widget settings and add code snippets to your website. First, ensure your help center security settings are correct by enabling or disabling the 'Require…
The security settings for displaying restricted content in Web Widget (Classic) depend on your help center type. For a public help center, do not enable 'Require sign in'. For a restricted help center, enable 'Require sign in'. If your help center…
You don't need single sign-on (SSO) to use restricted content in Web Widget (Classic), but it can enhance the user experience. SSO provides a seamless experience for users who want to view original articles from the Web Widget. However, even…
Generating a JWT token for Web Widget (Classic) involves creating a server-side payload with specific information. The payload should include the customer's name, email, current timestamp (iat), and a unique identifier (jti). Specify HS256 as the…
Yes, you can test Web Widget (Classic) restricted content on localhost by adding it to the allowlist. Specify 'localhost' or '127.0.0.1' as a valid domain in the allowlist to test in your development environment. This setup should allow you to view…