You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Integrate Azure SignalR Service with Service Connector
3
-
description: Integrate Azure SignalR Service into your application with Service Connector
3
+
description: Integrate Azure SignalR Service into your application with Service Connector. Learn about authentication types and client types of Azure SignalR Service.
# Integrate Azure SignalR Service with Service Connector
13
16
14
-
This page shows the supported authentication types and client types of Azure SignalR Service using Service Connector. You might still be able to connect to Azure SignalR Service in other programming languages without using Service Connector. This page also shows default environment variable name and value (or Spring Boot configuration) you get when you create the service connection. You can learn more about[Service Connector environment variable naming convention](concept-service-connector-internals.md).
17
+
This article shows the supported authentication types and client types of Azure SignalR Service using Service Connector. This article also shows default environment variable name and value or Spring Boot configuration that you get when you create the service connection. For more information, see[Service Connector environment variable naming convention](concept-service-connector-internals.md).
15
18
16
19
## Supported compute service
17
20
18
21
- Azure App Service
19
22
20
-
## Supported Authentication types and client types
23
+
## Supported authentication types and client types
21
24
22
25
| Client Type | System-assigned Managed Identity | User-assigned Managed Identity | Secret/ConnectionString | Service Principal |
23
26
| --- | --- | --- | --- | --- |
@@ -27,33 +30,31 @@ This page shows the supported authentication types and client types of Azure Sig
27
30
28
31
### .NET
29
32
30
-
**Secret/ConnectionString**
33
+
-Secret/ConnectionString
31
34
32
-
| Default environment variable name | Description | Example value |
33
-
| --- | --- | --- |
34
-
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string |`Endpoint=https://{signalrName}.service.signalr.net;AccessKey={};Version=1.0;`|
35
+
| Default environment variable name | Description | Example value |
36
+
| --- | --- | --- |
37
+
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string |`Endpoint=https://{signalrName}.service.signalr.net;AccessKey={};Version=1.0;`|
35
38
36
-
**System-assigned Managed Identity**
39
+
-System-assigned Managed Identity
37
40
38
-
| Default environment variable name | Description | Example value |
39
-
| --- | --- | --- |
40
-
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Managed Identity |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};Version=1.0;`|
41
+
| Default environment variable name | Description | Example value |
42
+
| --- | --- | --- |
43
+
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Managed Identity |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};Version=1.0;`|
41
44
42
-
**User-assigned Managed Identity**
45
+
-User-assigned Managed Identity
43
46
44
-
| Default environment variable name | Description | Example value |
45
-
| --- | --- | --- |
46
-
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Managed Identity |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};Version=1.0;`|
47
+
| Default environment variable name | Description | Example value |
48
+
| --- | --- | --- |
49
+
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Managed Identity |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};Version=1.0;`|
47
50
48
-
**Service Principal**
51
+
-Service Principal
49
52
50
-
| Default environment variable name | Description | Example value |
51
-
| --- | --- | --- |
52
-
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Service Principal |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};ClientSecret={};TenantId={};Version=1.0;`|
53
+
| Default environment variable name | Description | Example value |
54
+
| --- | --- | --- |
55
+
| AZURE_SIGNALR_CONNECTIONSTRING | SignalR Service connection string with Service Principal |`Endpoint=https://{signalrName}.service.signalr.net;AuthType=aad;ClientId={};ClientSecret={};TenantId={};Version=1.0;`|
53
56
54
57
## Next steps
55
58
56
-
Follow the tutorials listed below to learn more about Service Connector.
57
-
58
59
> [!div class="nextstepaction"]
59
60
> [Learn about Service Connector concepts](./concept-service-connector-internals.md)
Copy file name to clipboardExpand all lines: articles/service-connector/how-to-troubleshoot-front-end-error.md
+19-18Lines changed: 19 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,31 @@
1
1
---
2
-
title: Service Connector Troubleshooting Guidance
3
-
description: Error list and suggested actions of Service Connector
2
+
title: Service Connector troubleshooting guidance
3
+
description: This article lists error messages and suggested actions of Service Connector to use for troubleshooting issues.
4
4
author: shizn
5
5
ms.author: xshi
6
6
ms.service: service-connector
7
-
ms.custom: event-tier1-build-2022
8
-
ms.topic: how-to
9
-
ms.date: 05/03/2022
7
+
ms.topic: troubleshooting
8
+
ms.date: 5/25/2022
9
+
ms.custom:
10
+
- ignite-fall-2021
11
+
- kr2b-contr-experiment
12
+
- event-tier1-build-2022
10
13
---
11
14
12
15
# How to troubleshoot with Service Connector
13
16
14
-
If you come across an issue, you can refer to the error message to find suggested actions or fixes. This how-to guide shows you several options to troubleshoot Service Connector.
17
+
This article lists error messages and suggestions to troubleshoot Service Connector.
15
18
16
-
## Troubleshooting from the Azure portal
19
+
## Error message and suggested actions from the Azure portal
17
20
18
21
| Error message | Suggested Action |
19
22
| --- | --- |
20
-
| Unknown resource type | <ul><li>Check source and target resource to verify whether the service types are supported by Service Connector.</li><li>Check whether the specified source-target connection combination is supported by Service Connector.</li></ul> |
21
-
| Unknown resource type | <ul><li>Check whether the target resource exists.</li><li>Check the correctness of the target resource ID.</li></ul> |
23
+
| Unknown resource type | <ul><li>Check source and target resource to verify whether the service types are supported by Service Connector.</li><li>Check whether the specified source-target connection combination is supported by Service Connector.</li><li>Check whether the target resource exists.</li><li>Check the correctness of the target resource ID.</li></ul> |
22
24
| Unsupported resource | <ul><li>Check whether the authentication type is supported by the specified source-target connection combination.</li></ul> |
23
25
24
-
### Troubleshooting using the Azure CLI
25
-
26
-
#### InvalidArgumentValueError
26
+
## Error type,error message, and suggested actions using Azure CLI
27
27
28
+
### InvalidArgumentValueError
28
29
29
30
| Error message | Suggested Action |
30
31
| --- | --- |
@@ -38,18 +39,18 @@ If you come across an issue, you can refer to the error message to find suggeste
38
39
| Error message | Suggested Action |
39
40
| --- | --- |
40
41
|`{Argument}` shouldn't be blank | User should provide argument value for interactive input |
41
-
| Required keys missing for parameter `{Parameter}`. All possible keys are: `{Keys}`| Provide value for the auth info parameter, usually in the form of `--param key1=val1 key2=val2`. |
42
+
| Required keys missing for parameter `{Parameter}`. All possible keys are: `{Keys}`| Provide value for the authentication information parameter, usually in the form of `--param key1=val1 key2=val2`. |
42
43
| Required argument is missing, please provide the arguments: `{Arguments}`| Provide the required argument. |
43
44
44
45
#### ValidationError
45
46
46
47
| Error message | Suggested Action |
47
48
| --- | --- |
48
-
| Only one auth info is needed | User can only provide one auth info parameter. Check whether auth info is missing or multiple auth info parameters are provided. |
49
-
| Auth info argument should be provided when updating the connection: `{ConnectionName}` | When you update a secret type connection, auth info parameter should be provided. This error occurs because user's secret cannot be accessed through the ARM API.
50
-
| Either client type or auth info should be specified to update |When you update a connection, either client type or auth info should be provided. |
51
-
| Usage error: {} [KEY=VALUE ...]| Check the available keys and provide values for the auth info parameter, usually in the form of `--param key1=val1 key2=val2`. |
52
-
| Unsupported Key `{Key}` is provided for parameter `{Parameter}`. All possible keys are: `{Keys}`| Check the available keys and provide values for the auth info parameter, usually in the form of `--param key1=val1 key2=val2`. |
49
+
| Only one auth info is needed | User can only provide one authentication information parameter. Check whether it isn't provided or multiple parameters are provided. |
50
+
| Auth info argument should be provided when updating the connection: `{ConnectionName}`|The authentication information should be provided when updating a secret type connection. This error occurs because a user's secret can't be accessed through the Azure Resource Manager API.|
51
+
| Either client type or auth info should be specified to update |Either client type or authentication information should be provided when updating a connection. |
52
+
| Usage error: `{} [KEY=VALUE ...]`| Check the available keys and provide values for the auth info parameter, usually in the form of `--param key1=val1 key2=val2`. |
53
+
| Unsupported Key `{Key}` is provided for parameter `{Parameter}`. All possible keys are: `{Keys}`| Check the available keys and provide values for the authentication information parameter, usually in the form of `--param key1=val1 key2=val2`. |
53
54
| Provision failed, please create the target resource manually and then create the connection. Error details: `{ErrorTrace}`| <ul><li>Retry.</li><li>Create the target resource manually and then create the connection.</li></ul> |
Copy file name to clipboardExpand all lines: articles/service-connector/quickstart-portal-spring-cloud-connection.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,15 @@
1
1
---
2
-
title: Quickstart - Create a service connection in Spring Cloud from the Azure portal
3
-
description: Quickstart showing how to create a service connection in Spring Cloud from Azure portal
2
+
title: Create a service connection in Spring Cloud from Azure portal
3
+
description: This quickstart shows you how to create a service connection in Spring Cloud from the Azure portal.
4
4
author: shizn
5
5
ms.author: xshi
6
6
ms.service: service-connector
7
-
ms.custom: event-tier1-build-2022
8
-
ms.topic: overview
9
-
ms.date: 05/03/2022
7
+
ms.topic: quickstart
8
+
ms.date: 5/25/2022
9
+
ms.custom:
10
+
- ignite-fall-2021
11
+
- kr2b-contr-experiment
12
+
- event-tier1-build-2022
10
13
---
11
14
12
15
# Quickstart: Create a service connection in Spring Cloud from the Azure portal
@@ -37,15 +40,15 @@ Sign in to the Azure portal at [https://portal.azure.com/](https://portal.azure.
37
40
|**Storage account**| Your storage account | The target storage account you want to connect to. If you choose a different service type, select the corresponding target service instance. |
38
41
39
42
1. Select **Next: Authentication** to select the authentication type. Then select **Connection string** to use access key to connect your Blob storage account.
40
-
1. Then select **Next: Review + Create**to review the provided information. Then select **Create** to create the service connection. It might take 1 minute to complete the operation.
43
+
1. Then select **Next: Review + Create** to review the provided information. Then select **Create** to create the service connection. It might take one minute to complete the operation.
41
44
42
45
## View service connections in Spring Cloud
43
46
44
47
1. Select **Service Connector** to view the Spring Cloud connection to the target service.
45
48
46
49
1. Select **>** to expand the list and access the properties required by your Spring boot application.
47
50
48
-
1. Select the ellipsis **...** and **Validate**. You can see the connection validation details in the pop-up blade from the right.
51
+
1. Select the ellipsis **...** and **Validate**. You can see the connection validation details in the context pane from the right.
0 commit comments