{"id":6566,"date":"2026-04-22T12:56:14","date_gmt":"2026-04-22T19:56:14","guid":{"rendered":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/?post_type=ht_kb&p=6566"},"modified":"2026-04-22T13:15:43","modified_gmt":"2026-04-22T20:15:43","slug":"smartbrowser-ssl-certificates-configuration","status":"publish","type":"ht_kb","link":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/","title":{"rendered":"SmartBrowser SSL Certificates Configuration"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

This article describes how to configure SmartBrowser to trust self-signed certificates and manage SSL certificate errors. Two approaches are available: enabling the \u201ctrust anything\u201d<\/strong> option, or adding specific certificates to the configuration.<\/p>\n\n\n\n

Method 1: Trust Any Certificate (Quick Setup)<\/h2>\n\n\n\n

Warning:<\/strong> This method trusts ALL certificates, including invalid or malicious ones. Use only in development or highly controlled environments.<\/p>\n\n\n\n

Configuration<\/strong><\/h3>\n\n\n\n

Add the following to the\u00a0smartconfig.json:<\/p>\n\n\n\n

{<\/em><\/p>\n\n\n\n

\"certificates\": {<\/em><\/p>\n\n\n\n

\"allowAny\": true<\/em><\/p>\n\n\n\n

}<\/em><\/p>\n\n\n\n

}<\/em><\/p>\n\n\n\n

When\u00a0allowAny\u00a0is set to\u00a0true, SmartBrowser automatically trusts any SSL certificate presented by any server, regardless of validity, expiration, or trust chain issues.<\/p>\n\n\n\n

Security Note:<\/strong>\u00a0<\/span>This bypasses all SSL security checks and should never be used in production environments where security is a concern.<\/p>\n\n\n\n

Method 2: Configure Specific Certificates (Recommended)<\/h2>\n\n\n\n

This method allows specific certificates to be trusted while maintaining security for all others. Certificates can be configured using multiple methods outlined below.<\/p>\n\n\n\n

2.1 Using PEM Certificates<\/h3>\n\n\n\n

Add certificates in PEM format directly to the configuration file. This option is useful when the full certificate text is available.<\/p>\n\n\n\n

Configuration:<\/strong><\/h4>\n\n\n\n

{<\/em><\/p>\n\n\n\n

\"certificates\": {<\/em><\/p>\n\n\n\n

\"certificates\": [<\/em><\/p>\n\n\n\n

[<\/em><\/p>\n\n\n\n

\"—–BEGIN CERTIFICATE—–\",<\/em><\/p>\n\n\n\n

\"MIIDXTCCAkWgAwIBAgIJAKL7wQ8O3u3tMA0GCSqGSIb3DQEBCQUAMEUxCzAJBgNV\",<\/em><\/p>\n\n\n\n

\"BAYTAlVTMRMwEQYDVQQIDApTb21lLVN0YXRlMSEwHwYDVQQKDBhJbnRlcm5ldCBX\",<\/em><\/p>\n\n\n\n

\"aWRnaXRzIFB0eSBMdGQwHhcNMTcwODI3MjM1MjU5WhcNMjcwODI1MjM1MjU5WjBF\",<\/em><\/p>\n\n\n\n

\"MQswCQYDVQQGEwJVUzETMBEGA1UECAwKU29tZS1TdGF0ZTEhMB8GA1UECgwYSW50\",<\/em><\/p>\n\n\n\n

\"ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB\",<\/em><\/p>\n\n\n\n

\"CgKCAQEAyMEdSs1aIZyQVt2jW8VaUkRtxa2QdSYV30kDg46YDCuY1mL8oUrjB3C\",<\/em><\/p>\n\n\n\n

\"—–END CERTIFICATE—–\"<\/em><\/p>\n\n\n\n

]<\/em><\/p>\n\n\n\n

]<\/em><\/p>\n\n\n\n

}<\/em><\/p>\n\n\n\n

}<\/em><\/p>\n\n\n\n

How it works:<\/strong><\/p>\n\n\n\n

  • Each certificate is represented as an array of strings<\/li>
  • Each string is a line from the PEM certificate<\/li>
  • The system automatically combines these lines with newlines<\/li><\/ul>\n\n\n\n

    To get a PEM certificate:<\/h4>\n\n\n\n

    # From a website<\/em><\/p>\n\n\n\n

    openssl s_client -showcerts -connect example.com:443 \/dev\/null | openssl x509 -outform PEM > cert.pem<\/em><\/p>\n\n\n\n

    # From a certificate file<\/em><\/p>\n\n\n\n

    openssl x509 -in cert.crt -outform PEM -out cert.pem<\/em><\/p>\n\n\n\n

    2.2 Using Certificate Fingerprints<\/h3>\n\n\n\n

    Fingerprints are unique identifiers for certificates. You can use either SHA-1 or SHA-256 fingerprints.<\/p>\n\n\n\n

    Configuration:<\/strong><\/h3>\n\n\n\n

    {<\/em><\/p>\n\n\n\n

    \"certificates\": {<\/em><\/p>\n\n\n\n

    \"fingerprints_SHA1\": [<\/em><\/p>\n\n\n\n

    \"A1:B2:C3:D4:E5:F6:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12\"<\/em><\/p>\n\n\n\n

    ],<\/em><\/p>\n\n\n\n

    \"fingerprints_SHA256\": [<\/em><\/p>\n\n\n\n

    \"CC C1 25 F2 BF 5B A9 7B 21 DF 9F DC 2B 6E 76 C5 CB FD 7B F2 AC 68 BF FD 52 8E 6E 69 4E CE 19 0B\"<\/em><\/p>\n\n\n\n

    ]<\/em><\/p>\n\n\n\n

    }<\/em><\/p>\n\n\n\n

    }<\/em><\/p>\n\n\n\n

    Notes:<\/strong><\/h4>\n\n\n\n
    • Fingerprints can include spaces, colons, or be continuous (they are automatically normalized)<\/li>
    • SHA-256 fingerprints are recommended for better security<\/li>
    • SHA-1 fingerprints are supported but deprecated<\/li><\/ul>\n\n\n\n
      To obtain a certificate fingerprint:<\/strong><\/h5>\n\n\n\n

      # SHA-256 fingerprint<\/em> (recommended)<\/p>\n\n\n\n

      openssl x509 -in cert.pem -fingerprint -sha256 -noout | cut -d'=' -f2 | tr -d ':'<\/em><\/p>\n\n\n\n

      # From a website directly<\/em><\/p>\n\n\n\n

      echo | openssl s_client -connect example.com:443 2>\/dev\/null | openssl x509 -fingerprint -sha256 -noout | cut -d'=' -f2<\/em><\/p>\n\n\n\n

      2.3 Using Certificate Serial Numbers<\/h3>\n\n\n\n

      Certificates can be trusted by their serial number (in hexadecimal format).<\/p>\n\n\n\n

      Configuration:<\/strong><\/h4>\n\n\n\n

      {<\/em><\/p>\n\n\n\n

      \"certificates\": {<\/em><\/p>\n\n\n\n

      \"serialNumbers\": [<\/em><\/p>\n\n\n\n

      \"A1B2C3D4E5F67890\"<\/em><\/p>\n\n\n\n

      ]<\/em><\/p>\n\n\n\n

      }<\/em><\/p>\n\n\n\n

      }<\/em><\/p>\n\n\n\n

      To obtain a certificate serial number:<\/h4>\n\n\n\n

      openssl x509 -in cert.pem -noout -serial | cut -d'=' -f2<\/em><\/p>\n\n\n\n

      2.4 Using Certificate Files<\/h3>\n\n\n\n

      Certificate files stored on the device filesystem can be referenced.<\/p>\n\n\n\n

      Configuration:<\/strong><\/h4>\n\n\n\n

      {<\/em><\/p>\n\n\n\n

      \"certificates\": {<\/em><\/p>\n\n\n\n

      \"files\": [<\/em><\/p>\n\n\n\n

      \"\/sdcard\/certificates\/my-cert.pem\",<\/em><\/p>\n\n\n\n

      \"\/data\/data\/com.staylinked.smartbrowser\/files\/certs\/server-cert.crt\"<\/em><\/p>\n\n\n\n

      ]<\/em><\/p>\n\n\n\n

      }<\/em><\/p>\n\n\n\n

      }<\/em><\/p>\n\n\n\n

      How it works:<\/strong><\/h4>\n\n\n\n
      • The system reads each file and extracts the SHA-256 fingerprint<\/li>
      • The fingerprint is automatically added to the trusted list<\/li>
      • Files must be accessible by the application<\/li><\/ul>\n\n\n\n

        File format:<\/strong>\u00a0Certificates can be in PEM or DER format (PEM is recommended).<\/p>\n\n\n\n

        Method 3: SSL Error Handling Flags<\/h2>\n\n\n\n

        SmartBrowser can be configured to ignore specific types of SSL errors. This is useful when certificates have minor issues but the certificate itself should still be verified.<\/p>\n\n\n\n

        Configuration:<\/strong><\/h2>\n\n\n\n

        {<\/em><\/p>\n\n\n\n

        \"sslErrorHandling\": 255<\/em><\/p>\n\n\n\n

        }<\/em><\/p>\n\n\n\n

        The\u00a0sslErrorHandling\u00a0value is a bitmask that controls which SSL errors to ignore. Details are shown in the table below.<\/p>\n\n\n\n

        Flag Value<\/strong><\/td>Error Type<\/strong><\/td>Description<\/strong><\/td><\/tr>
        0x01<\/td>SSL_NOTYETVALID<\/td>Certificate not yet valid (future date)<\/td><\/tr>
        0x02<\/td>SSL_EXPIRED<\/td>Certificate has expired<\/td><\/tr>
        0x04<\/td>SSL_IDMISMATCH<\/td>Hostname mismatch<\/td><\/tr>
        0x08<\/td>SSL_UNTRUSTED<\/td>Certificate authority not trusted<\/td><\/tr>
        0x10<\/td>SSL_DATE_INVALID<\/td>Certificate date is invalid<\/td><\/tr>
        0x20<\/td>SSL_INVALID<\/td>Certificate is invalid<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Common values:<\/strong><\/h3>\n\n\n\n
        • 0 (or SSL_ERROR_HANDLING_NONE) – Don't ignore any errors (strict)<\/li>
        • 255 (or SSL_ERROR_HANDLING_ALL) – Ignore all SSL errors<\/li>
        • 15 (0x0F) – Ignore common errors (not yet valid, expired, hostname mismatch, untrusted)<\/li><\/ul>\n\n\n\n

          Example – Ignore expired and hostname mismatch:<\/strong><\/h3>\n\n\n\n

          {<\/em><\/p>\n\n\n\n

          \"sslErrorHandling\": 6<\/em><\/p>\n\n\n\n

          }<\/em><\/p>\n\n\n\n

          This is calculated as:\u00a00x02 (EXPIRED) + 0x04 (IDMISMATCH) = 6<\/p>\n\n\n\n

          Note:<\/strong> Even with error handling flags set, certificates must still pass the certificate checker (via certificates configuration) unless allowAny is true.<\/p>\n\n\n\n

          Configuration File Location<\/strong><\/h3>\n\n\n\n

          The certificate configuration should be added to your\u00a0smartconfig.json\u00a0file. This file is typically located at:<\/p>\n\n\n\n

          • Assets:<\/strong> app\/src\/main\/assets\/config\/smartconfig.json (default\/bundled config)<\/li>
          • Device:<\/strong> \/sdcard\/smartbrowser\/config\/smartconfig.json (user config, overrides bundled)<\/li><\/ul>\n\n\n\n

            When deploying via SBP packages, the configuration is typically included in the package and merged with existing settings.<\/p>\n\n\n\n

            Examples<\/h2>\n\n\n\n

            Example 1: Development Environment – Trust Everything<\/h3>\n\n\n\n

            For development environments where quick testing with self-signed certificates is required:<\/p>\n\n\n\n

            {<\/em><\/p>\n\n\n\n

            \"certificates\": {<\/em><\/p>\n\n\n\n

            \"allowAny\": true<\/em><\/p>\n\n\n\n

            },<\/em><\/p>\n\n\n\n

            \"sslErrorHandling\": 255<\/em><\/p>\n\n\n\n

            }<\/em><\/p>\n\n\n\n

            Example 2: Production – Trust Specific Self-Signed Certificate<\/h3>\n\n\n\n

            For production use with a specific self-signed certificate:<\/p>\n\n\n\n

            {<\/em><\/p>\n\n\n\n

            \"certificates\": {<\/em><\/p>\n\n\n\n

            \"allowAny\": false,<\/em><\/p>\n\n\n\n

            \"fingerprints_SHA256\": [<\/em><\/p>\n\n\n\n

            \"CC C1 25 F2 BF 5B A9 7B 21 DF 9F DC 2B 6E 76 C5 CB FD 7B F2 AC 68 BF FD 52 8E 6E 69 4E CE 19 0B\"<\/em><\/p>\n\n\n\n

            ],<\/em><\/p>\n\n\n\n

            \"certificates\": [<\/em><\/p>\n\n\n\n

            [<\/em><\/p>\n\n\n\n

            \"—–BEGIN CERTIFICATE—–\",<\/em><\/p>\n\n\n\n

            \"MIIDXTCCAkWgAwIBAgIJAKL7wQ8O3u3tMA0GCSqGSIb3DQEBCQUAMEUxCzAJBgNV\",<\/em><\/p>\n\n\n\n

            \"… (rest of certificate lines) …\",<\/em><\/p>\n\n\n\n

            \"—–END CERTIFICATE—–\"<\/em><\/p>\n\n\n\n

            ]<\/em><\/p>\n\n\n\n

            ]<\/em><\/p>\n\n\n\n

            },<\/em><\/p>\n\n\n\n

            \"sslErrorHandling\": 0<\/em><\/p>\n\n\n\n

            }<\/em><\/p>\n\n\n\n

            Example 3: Internal CA Certificate<\/h3>\n\n\n\n

            When using an internal Certificate Authority:<\/p>\n\n\n\n

            {<\/em><\/p>\n\n\n\n

            \"certificates\": {<\/em><\/p>\n\n\n\n

            \"allowAny\": false,<\/em><\/p>\n\n\n\n

            \"files\": [<\/em><\/p>\n\n\n\n

            \"\/sdcard\/certificates\/internal-ca.pem\"<\/em><\/p>\n\n\n\n

            ],<\/em><\/p>\n\n\n\n

            \"fingerprints_SHA256\": [<\/em><\/p>\n\n\n\n

            \"AA BB CC DD EE FF 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF 11 22 33 44 55 66 77 88 99 AA BB\"<\/em><\/p>\n\n\n\n

            ]<\/em><\/p>\n\n\n\n

            },<\/em><\/p>\n\n\n\n

            \"sslErrorHandling\": 4<\/em><\/p>\n\n\n\n

            }<\/em><\/p>\n\n\n\n

            This configuration:<\/p>\n\n\n\n

            • Loads the CA certificate from a file<\/li>
            • Also trusts certificates with the specified SHA-256 fingerprint<\/li>
            • Allows hostname mismatches (useful for internal domains)<\/li><\/ul>\n\n\n\n

              Example 4: Multiple Certificates with Error Handling<\/h3>\n\n\n\n

              Trust multiple certificates while allowing some common errors:<\/p>\n\n\n\n

              {<\/em><\/p>\n\n\n\n

              \"certificates\": {<\/em><\/p>\n\n\n\n

              \"allowAny\": false,<\/em><\/p>\n\n\n\n

              \"fingerprints_SHA256\": [<\/em><\/p>\n\n\n\n

              \"CC C1 25 F2 BF 5B A9 7B 21 DF 9F DC 2B 6E 76 C5 CB FD 7B F2 AC 68 BF FD 52 8E 6E 69 4E CE 19 0B\",<\/em><\/p>\n\n\n\n

              \"AA BB CC DD EE FF 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF 11 22 33 44 55 66 77 88 99 AA BB\"<\/em><\/p>\n\n\n\n

              ],<\/em><\/p>\n\n\n\n

              \"serialNumbers\": [<\/em><\/p>\n\n\n\n

              \"A1B2C3D4E5F67890\",<\/em><\/p>\n\n\n\n

              \"1234567890ABCDEF\"<\/em><\/p>\n\n\n\n

              ]<\/em><\/p>\n\n\n\n

              },<\/em><\/p>\n\n\n\n

              \"sslErrorHandling\": 15<\/em><\/p>\n\n\n\n

              }<\/em><\/p>\n\n\n\n

              This configuration:<\/p>\n\n\n\n

              • Trusts certificates matching any of the SHA-256 fingerprints<\/li>
              • Trusts certificates with the specified serial numbers<\/li>
              • Ignores common SSL errors (not yet valid, expired, hostname mismatch, untrusted)<\/li><\/ul>\n\n\n\n

                How It Works<\/strong><\/h4>\n\n\n\n
                1. Certificate Checker (OverrideCertChecker):<\/strong>
                  • When an SSL error occurs, the browser first checks if the certificate is in the trusted list<\/li>
                  • It compares the certificate against fingerprints, serial numbers, and PEM certificates<\/li>
                  • If allowAny is true, all certificates are automatically trusted<\/li><\/ul><\/li>
                  • SSL Error Handler (BaseBrowser.onReceivedSslError):<\/strong>
                    • If the certificate passes the certificate checker, the connection proceeds<\/li>
                    • If not, the sslErrorHandling flags are checked<\/li>
                    • If the error type matches a flag, the connection proceeds<\/li>
                    • Otherwise, the SSL error is passed to the default handler (connection fails)<\/li><\/ul><\/li>
                    • Priority:<\/strong>
                      • Certificate checker (allowAny or specific certificates) takes precedence<\/li>
                      • SSL error handling flags are checked if certificate checker doesn't match<\/li>
                      • If neither matches, the connection is rejected<\/li><\/ul><\/li><\/ol>\n\n\n\n

                        Troubleshooting<\/h2>\n\n\n\n

                        Certificate Not Being Trusted<\/h3>\n\n\n\n
                        1. Verify the fingerprint:<\/strong> Make sure you're using the correct fingerprint format<\/li><\/ol>\n\n\n\n

                          openssl x509 -in cert.pem -fingerprint -sha256 -noout<\/em><\/p>\n\n\n\n

                          1. Check file paths:<\/strong> If using files, ensure the file path is correct and accessible<\/li>
                          2. Verify PEM format:<\/strong> PEM certificates must include the —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—– lines<\/li>
                          3. Check logs:<\/strong> Look for SSL error messages in the application logs to see what error is occurring<\/li><\/ol>\n\n\n\n

                            Common Issues<\/h3>\n\n\n\n
                            • Hostname mismatch:<\/strong> Add SSL_ERROR_HANDLING_IDMISMATCH (0x04) to sslErrorHandling or use the certificate fingerprint<\/li>
                            • Expired certificate:<\/strong> Add SSL_ERROR_HANDLING_EXPIRED (0x02) to sslErrorHandling or use allowAny: true<\/li>
                            • Untrusted CA:<\/strong> Add the CA certificate to the certificates array or use allowAny: true<\/li><\/ul>\n\n\n\n

                              Security Best Practices<\/h3>\n\n\n\n
                              1. Avoid\u00a0allowAny: true\u00a0in production<\/strong>\u00a0– Only use in development or highly controlled environments<\/li>
                              2. Use SHA-256 fingerprints<\/strong>\u00a0– More secure than SHA-1<\/li>
                              3. Use specific certificates<\/strong>\u00a0– Only trust the certificates actually required<\/li>
                              4. Combine methods<\/strong>\u00a0– Use fingerprints for quick setup, PEM certificates for full certificate chain support<\/li>
                              5. Monitor certificate expiration<\/strong>\u00a0– Update fingerprints or certificates before they expire<\/li>
                              6. Use file-based certificates<\/strong>\u00a0– For easier management and updates without modifying JSON<\/li><\/ol>\n\n\n\n

                                Additional Notes<\/h3>\n\n\n\n
                                • Certificate configurations are loaded when the application starts or when configuration is reloaded<\/li>
                                • Changes to\u00a0smartconfig.json\u00a0require an application restart or configuration reload to take effect<\/li>
                                • Certificate files referenced in the\u00a0files\u00a0array are read at startup<\/li>
                                • PEM certificates in the\u00a0certificates\u00a0array are parsed and their fingerprints are automatically added to the trusted list<\/li><\/ul>\n\n\n\n

                                  Quick Reference<\/h3>\n\n\n\n

                                  Trust all certificates:<\/h4>\n\n\n\n

                                  { \"certificates\": { \"allowAny\": true } }<\/em><\/p>\n\n\n\n

                                  Trust by SHA-256 fingerprint:<\/h4>\n\n\n\n

                                  { \"certificates\": { \"fingerprints_SHA256\": [\"AA:BB:CC:…\"] } }<\/em><\/p>\n\n\n\n

                                  Trust by PEM certificate:<\/h4>\n\n\n\n

                                  { \"certificates\": { \"certificates\": [[ \"—–BEGIN CERTIFICATE—–\", \"…\", \"—–END CERTIFICATE—–\" ]] } }<\/em><\/p>\n\n\n\n

                                  Ignore all SSL errors:<\/h4>\n\n\n\n

                                  { \"sslErrorHandling\": 255 }<\/em><\/p>\n\n\n\n

                                  Ignore expired and hostname mismatch:<\/h4>\n\n\n\n

                                  { \"sslErrorHandling\": 6 }<\/em><\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/p>\n","protected":false},"excerpt":{"rendered":"

                                  Introduction This article describes how to configure SmartBrowser to trust self-signed certificates and manage SSL certificate errors. Two approaches are available: enabling the \u201ctrust anything\u201d option, or adding specific certificates to the configuration. Method 1: Trust Any Certificate (Quick Setup) Warning: This method trusts ALL certificates, including invalid or malicious ones….<\/p>\n","protected":false},"author":8,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":[],"ht-kb-category":[58],"ht-kb-tag":[],"yoast_head":"\nSmartBrowser SSL Certificates Configuration – StayLinked<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.staylinked.com\/knowledge-base\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SmartBrowser SSL Certificates Configuration – StayLinked\" \/>\n<meta property=\"og:description\" content=\"Introduction This article describes how to configure SmartBrowser to trust self-signed certificates and manage SSL certificate errors. Two approaches are available: enabling the \u201ctrust anything\u201d option, or adding specific certificates to the configuration. Method 1: Trust Any Certificate (Quick Setup) Warning: This method trusts ALL certificates, including invalid or malicious ones....\" \/>\n<meta property=\"og:url\" content=\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/\" \/>\n<meta property=\"og:site_name\" content=\"StayLinked\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-22T20:15:43+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/#website\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/\",\"name\":\"StayLinked Knowledge Base\",\"description\":\"Partner Portal Resources and Support\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/#webpage\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/\",\"name\":\"SmartBrowser SSL Certificates Configuration – StayLinked\",\"isPartOf\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/#website\"},\"datePublished\":\"2026-04-22T19:56:14+00:00\",\"dateModified\":\"2026-04-22T20:15:43+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/smartbrowser-ssl-certificates-configuration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb_sb\/knowledge-base\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"SmartBrowser SSL Certificates Configuration\"}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb\/6566"}],"collection":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/comments?post=6566"}],"version-history":[{"count":9,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb\/6566\/revisions"}],"predecessor-version":[{"id":6575,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb\/6566\/revisions\/6575"}],"wp:attachment":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/media?parent=6566"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb-category?post=6566"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb_sb\/wp-json\/wp\/v2\/ht-kb-tag?post=6566"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}