Merge pull request #407 from snyk/chore/update-support-site-links

updated support URLs
snyk · Dec 6, 2024 · 242e3a8 · 242e3a8
2 parents d4eb1f5 + d99a8df
commit 242e3a8
Show file tree

Hide file tree

Showing 103 changed files with 387 additions and 390 deletions.
diff --git a/docs/README.md b/docs/README.md
@@ -32,7 +32,7 @@ Stay up to date with the [latest updates in Snyk documentation](whats-new-in-the
 
 ## Learning and information
 
-| <p><a href="https://learn.snyk.io/catalog/product-training/?type=product-training">Snyk product training</a><br>Courses to help you use Snyk functions</p> | <p><a href="https://support.snyk.io/hc/en-us">Snyk support</a><br>Access Support tickets and knowledgebase</p>       | <p><a href="https://snyk.io/advisor/">Snyk Advisor</a><br>Find the best package for your next project</p>         |
+| <p><a href="https://learn.snyk.io/catalog/product-training/?type=product-training">Snyk product training</a><br>Courses to help you use Snyk functions</p> | <p><a href="https://support.snyk.io">Snyk support</a><br>Access Support tickets and knowledgebase</p>       | <p><a href="https://snyk.io/advisor/">Snyk Advisor</a><br>Find the best package for your next project</p>         |
 | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
 | <p><a href="https://updates.snyk.io/">Snyk product updates</a><br>See the latest Snyk product information</p>                                             | <p><a href="https://security.snyk.io/">Snyk vulnerability DB</a><br>Our database for open source vulnerabilities</p> | <p><a href="https://status.snyk.io/">Snyk Status</a><br>Shows operational status and history for Snyk systems.</p> |
 

diff --git a/...so-for-authentication-to-snyk/configure-self-serve-single-sign-on-sso/README.md b/...so-for-authentication-to-snyk/configure-self-serve-single-sign-on-sso/README.md
@@ -3,7 +3,7 @@
 Group Admins on a Snyk Enterprise plan who use SAML for SSO can configure Snyk Single Sign-on themselves. Ensure you have at least one Group and Organization where you can assign new users. See [Manage Groups and Organizations](../../../snyk-admin/groups-and-organizations/).
 
 {% hint style="info" %}
-To enable the self-serve SSO option, contact your Snyk account team or [Snyk support](https://support.snyk.io/hc/en-us).\
+To enable the self-serve SSO option, contact your Snyk account team or [Snyk support](https://support.snyk.io).\
 \
 This option does not accommodate [custom role mapping](../custom-mapping/). To set up custom role mapping with SSO for your Snyk Group, contact your Snyk account team.
 {% endhint %}

diff --git a/...ingle-sign-on-sso-for-authentication-to-snyk/identity-provider-idp-migration.md b/...ingle-sign-on-sso-for-authentication-to-snyk/identity-provider-idp-migration.md
@@ -6,8 +6,8 @@ To migrate identity providers:
 
 1. Download the correct Worksheet from the [SSO resources](set-up-snyk-single-sign-on-sso.md#resources).
 2. Fill out Worksheet with the IdP metadata information.
-3. Submit the Worksheet; [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new) to raise a Support ticket.
+3. Submit the Worksheet; [contact Snyk Support](https://support.snyk.io) to raise a Support ticket.
 
-To prevent new users from being created within Snyk, you must maintain your SAML protocol and use both the same Entity ID and ACS URL. If you are changing SAML protocols, [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new).
+To prevent new users from being created within Snyk, you must maintain your SAML protocol and use both the same Entity ID and ACS URL. If you are changing SAML protocols, [contact Snyk Support](https://support.snyk.io).
 
 After you have done this, the Support team will contact you and confirm the updated metadata has granted access through the new IdP.
diff --git a/...single-sign-on-sso-for-authentication-to-snyk/set-up-snyk-single-sign-on-sso.md b/...single-sign-on-sso-for-authentication-to-snyk/set-up-snyk-single-sign-on-sso.md
@@ -73,7 +73,7 @@ Obtain the following information from your identity provider. Provide this infor
 | Sign-in URL                   | The URL for your identity provider sign-in page                                                                                                                                                                                                                                                                                                                                                                                                           |
 | X509 Signing Certificate      | The identity provider public key, encoded in Base64 format                                                                                                                                                                                                                                                                                                                                                                                                |
 | Sign-out URL                  | <p>Optional, but recommended -</p><p>The URL for redirect whenever a user logs out of Snyk</p>                                                                                                                                                                                                                                                                                                                                                            |
-| User ID attribute             | <p>Optional default is <strong>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier</strong><br><br><strong>Important:</strong> This value uniquely identifies Snyk users and if changed will result in a duplicate user being created. If you see a duplicate user after changing identity provider <a href="https://support.snyk.io/hc/en-us/requests/new">submit a request </a>to Snyk support to have the duplicate user removed.</p> |
+| User ID attribute             | <p>Optional default is <strong>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier</strong><br><br><strong>Important:</strong> This value uniquely identifies Snyk users and if changed will result in a duplicate user being created. If you see a duplicate user after changing identity provider <a href="https://support.snyk.io">submit a request </a>to Snyk support to have the duplicate user removed.</p> |
 | Protocol binding              | HTTP-POST is recommended, HTTP-Redirect is also supported                                                                                                                                                                                                                                                                                                                                                                                                 |
 | IdP initiated flow supported? | Idp-initiated flows carry a security risk and are therefore not recommended. Make sure you understand the risks before enabling                                                                                                                                                                                                                                                                                                                           |
 | Email domains and subdomains  | The email domains and subdomains that need access to the SSO                                                                                                                                                                                                                                                                                                                                                                                              |

diff --git a/...or-helm-chart-installation/multi-tenant-settings-for-helm-chart-installation.md b/...or-helm-chart-installation/multi-tenant-settings-for-helm-chart-installation.md
@@ -18,7 +18,7 @@ Australia: `https://broker.au.snyk.io`
 
 The Code Agent is deprecated and is no longer maintained.
 
-The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io/hc/en-us).
+The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io).
 
 The automatic [PR Checks](https://docs.snyk.io/scan-with-snyk/pull-requests/pull-request-checks) feature is not supported for Snyk Broker - Code Agent.
 {% endhint %}

diff --git a/...igure-snyk-broker/artifactory-repository-install-and-configure-broker/README.md b/...igure-snyk-broker/artifactory-repository-install-and-configure-broker/README.md
@@ -28,7 +28,7 @@ For convenience, instructions to obtain or generate the Broker token follow. Whe
 {% hint style="info" %}
 If you do not see the **Snyk Broker** on/off switch, you do not have the necessary permissions and can only add a publicly accessible instance.
 
-Submit a request to [Snyk Support](https://support.snyk.io/hc/en-us/requests/new) if you want to add a private registry.
+Submit a request to [Snyk Support](https://support.snyk.io) if you want to add a private registry.
 {% endhint %}
 
 When you have the permissions needed to add a private registry, continue with the instructions to [generate a Broker token from the Web UI](./#generate-a-broker-token-from-the-web-ui).

diff --git a/...us-repository-prerequisites-and-steps-to-install-and-configure-broker/README.md b/...us-repository-prerequisites-and-steps-to-install-and-configure-broker/README.md
@@ -27,7 +27,7 @@ For convenience, instructions to obtain or generate the Broker token follow. Whe
 {% hint style="info" %}
 If you do not see the **Snyk Broker** switch, you do not have the necessary permissions and can only add a publicly accessible instance.
 
-Submit a request to [Snyk Support](https://support.snyk.io/hc/en-us/requests/new) if you want to add a private registry.
+Submit a request to [Snyk Support](https://support.snyk.io) if you want to add a private registry.
 {% endhint %}
 
 When you have permissions to add a private registry, continue with the instructions to [generate a Broker token from the Web UI](./#generate-a-broker-token-from-the-web-ui).

diff --git a/docs/enterprise-setup/snyk-broker/prepare-snyk-broker-for-deployment.md b/docs/enterprise-setup/snyk-broker/prepare-snyk-broker-for-deployment.md
@@ -16,7 +16,7 @@ The following are prerequisites for using Snyk Broker in any environment:
 * Client machine system requirements: one CPU, 256MB of RAM
 * Network access: an outbound TLS (443) to [https://broker.snyk.io](https://broker.snyk.io) AND [https://api.snyk.io](https://api.snyk.io) (or regional equivalent) that is also allowed by any firewalls installed on your network
 * A Snyk account
-* Self-enabled Broker integration using the Snyk API or enabled by contacting [Snyk Support](https://support.snyk.io/hc/en-us)
+* Self-enabled Broker integration using the Snyk API or enabled by contacting [Snyk Support](https://support.snyk.io)
 * A unique UUID token called a Broker token. See [Generate credentials in the target application for Snyk Broker](prepare-snyk-broker-for-deployment.md#generate-credentials-in-the-target-application-for-snyk-broker).
 * An SCM token or password. See the [integrations documentation](../../integrate-with-snyk/) for each SCM for information on how to obtain the token. Snyk Broker does not support authentication with the mTLS method. &#x20;
 * Docker configured to pull images from Docker Hub to install with Docker.
@@ -68,12 +68,12 @@ After generating the credentials for the Broker's target application, configure
 
 The Broker token is required and must be generated in order for you to use Snyk Broker.
 
-For code repository (SCM) integrations, a Broker token can be generated using the API or by contacting [Snyk support](https://support.snyk.io/hc/en-us/requests/new).
+For code repository (SCM) integrations, a Broker token can be generated using the API or by contacting [Snyk support](https://support.snyk.io).
 
-1. Follow the example under "Set up a broker for an existing integration" in the endpoint [Update existing integration](https://snyk.docs.apiary.io/#reference/integrations/integration/update-existing-integration) or contact [Snyk support](https://support.snyk.io/hc/en-us/requests/new).
+1. Follow the example under "Set up a broker for an existing integration" in the endpoint [Update existing integration](https://snyk.docs.apiary.io/#reference/integrations/integration/update-existing-integration) or contact [Snyk support](https://support.snyk.io).
 2. Verify the Broker token is generated in the Snyk Web UI under the specified SCM integration. by selecting **Settings** > **Integrations** for that specific integration to see the Broker token.
 
-For [Artifactory Repository](../../scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/) and [Nexus Repository Manager](../../scan-with-snyk/snyk-open-source/package-repository-integrations/nexus-repository-manager-connection-setup/) brokered instances or [Jira](install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md) integration, you can generate a Broker token in the Snyk UI or contact [Snyk support](https://support.snyk.io/hc/en-us/requests/new).
+For [Artifactory Repository](../../scan-with-snyk/snyk-open-source/package-repository-integrations/artifactory-package-repository-connection-setup/) and [Nexus Repository Manager](../../scan-with-snyk/snyk-open-source/package-repository-integrations/nexus-repository-manager-connection-setup/) brokered instances or [Jira](install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md) integration, you can generate a Broker token in the Snyk UI or contact [Snyk support](https://support.snyk.io).
 
 1. Select **Settings** > **Integrations** for that specific integration to generate the Broker token.
 2. After the Broker token is generated, under the integration, the notification from this screen correctly displays **Could not connect to…**, as you have not yet installed and configured the client.

diff --git a/docs/enterprise-setup/snyk-broker/snyk-broker-code-agent/README.md b/docs/enterprise-setup/snyk-broker/snyk-broker-code-agent/README.md
@@ -5,7 +5,7 @@
 
 The Code Agent is deprecated and is no longer maintained.
 
-The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md).  The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io/hc/en-us).
+The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md).  The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io).
 
 The automatic [PR Checks](../../../scan-with-snyk/pull-requests/pull-request-checks/) feature is not supported for Snyk Broker - Code Agent.
 {% endhint %}

diff --git a/docs/enterprise-setup/snyk-broker/snyk-broker-code-agent/i.md b/docs/enterprise-setup/snyk-broker/snyk-broker-code-agent/i.md
@@ -5,7 +5,7 @@
 
 The Code Agent is deprecated and is no longer maintained.
 
-The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io/hc/en-us).
+The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io).
 
 The automatic [PR Checks](../../../scan-with-snyk/pull-requests/pull-request-checks/) feature is not supported for Snyk Broker - Code Agent.
 {% endhint %}

diff --git a/...er/snyk-broker-code-agent/install-snyk-broker-code-agent-using-docker/README.md b/...er/snyk-broker-code-agent/install-snyk-broker-code-agent-using-docker/README.md
@@ -5,7 +5,7 @@
 
 The Code Agent is deprecated and is no longer maintained.
 
-The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io/hc/en-us).
+The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](../../install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker.md). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io).
 
 The automatic [PR Checks](../../../../scan-with-snyk/pull-requests/pull-request-checks/) feature is not supported for Snyk Broker - Code Agent.
 {% endhint %}

diff --git a/...ll-snyk-broker-code-agent-using-docker/test-the-snyk-broker-code-agent-setup.md b/...ll-snyk-broker-code-agent-using-docker/test-the-snyk-broker-code-agent-setup.md
@@ -5,7 +5,7 @@
 
 The Code Agent is deprecated and is no longer maintained.
 
-The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](https://docs.snyk.io/enterprise-setup/snyk-broker/install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io/hc/en-us).
+The preferred method of running Snyk Code analysis using Snyk Broker is through [Brokered Code](https://docs.snyk.io/enterprise-setup/snyk-broker/install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/snyk-code-clone-capability-with-broker-for-docker). The Code Agent is an alternative method without advantages. For details, contact your Snyk Integration Consultant or Technical Success Manager or contact [Snyk Support](https://support.snyk.io).
 
 The automatic [PR Checks](https://docs.snyk.io/scan-with-snyk/pull-requests/pull-request-checks) feature is not supported for Snyk Broker - Code Agent.
 {% endhint %}

diff --git a/docs/enterprise-setup/snyk-broker/snyk-broker-container-registry-agent/README.md b/docs/enterprise-setup/snyk-broker/snyk-broker-container-registry-agent/README.md
@@ -51,7 +51,7 @@ GitHub Container registry and GitLab Container Registry do not follow Docker v2
 
 ## **Prerequisites for Container Registry Agent**
 
-To set up the Snyk Broker and the Container Registry Agent, you must have a Broker token. Contact [Snyk Support](https://support.snyk.io/hc/en-us) to obtain your Broker token.
+To set up the Snyk Broker and the Container Registry Agent, you must have a Broker token. Contact [Snyk Support](https://support.snyk.io) to obtain your Broker token.
 
 {% hint style="warning" %}
 For the Container Registry Agent to work, you must have two separate containers deployed in your infrastructure, creating two separate services. For details, see [Components of the network-restricted container registries solution](./#components-of-the-network-restricted-container-registries-solution).
@@ -73,7 +73,7 @@ The system and software requirements to set up and run the Snyk Broker Container
 {% hint style="info" %}
 **Scaling to adjust scan capacity**
 
-With the listed configuration of 1 vCPU and 2GB RAM, scanning capacity would be approximately 160 images of \~350MB each in one run. You can scale this up based on your image sizes. If you have a specific use case that does not allow scaling and does not fit the limitations, contact [Snyk Support](https://support.snyk.io/hc/en-us/).
+With the listed configuration of 1 vCPU and 2GB RAM, scanning capacity would be approximately 160 images of \~350MB each in one run. You can scale this up based on your image sizes. If you have a specific use case that does not allow scaling and does not fit the limitations, contact [Snyk Support](https://support.snyk.io).
 {% endhint %}
 
 ## **Set up the remote connection for Container Registry Agent using Docker**