Skip to content

Commit b4d8a0f

Browse files
authored
Merge pull request #285867 from meaghanlewis/refresh-remote-connection-keys
Add refresh remote connection keys article
2 parents 0c95c59 + 1b98d03 commit b4d8a0f

File tree

4 files changed

+41
-0
lines changed

4 files changed

+41
-0
lines changed
83.1 KB
Loading
56.1 KB
Loading
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Refresh remote connection keys in Azure Modeling and Simulation Workbench
3+
description: Learn how to refresh remote connection keys in Azure Modeling and Simulation Workbench.
4+
author: meaghanlewis
5+
ms.author: mosagie
6+
ms.service: modeling-simulation-workbench
7+
ms.topic: how-to
8+
ms.date: 09/05/2024
9+
# Customer intent: As a Chamber User in Azure Modeling and Simulation Workbench, I want to refresh remote connection keys.
10+
---
11+
12+
# Refresh remote connection keys
13+
14+
The Modeling and Simulation Workbench offers provisioned users secure remote connectivity to all chamber workloads. To set up remote access, register a new application in Microsoft Entra ID and add a client secret as described in [Create an Azure Modeling and Simulation Workbench](/azure/modeling-simulation-workbench/quickstart-create-portal#add-a-client-secret). Registering your application establishes a trust relationship between the Modeling and Simulation Workbench remote desktop authentication and the Microsoft identity platform. Creating a client secret allows the Modeling and Simulation Workbench to redirect Microsoft Entra sign-in requests directly to your organization's Microsoft Entra ID and enables a single sign-on experience for onboarded users.
15+
16+
## Client secret lifetime
17+
18+
The client secret lifetime is typically set to 12 months. If the workbench’s lifetime extends beyond the secret’s lifespan, the app secrets will expire resulting in users losing access to the chambers. Expired client secrets disrupt remote authentication, causing a blue screen.
19+
20+
To address an expired client secret, you need to create a new secret by following steps outlined in [Create an application in Microsoft Entra ID](/azure/modeling-simulation-workbench/quickstart-create-portal#create-an-application-in-microsoft-entra-id). After creating a new secret, you need to update the Modeling and Simulation Workbench with that new client secret URL.
21+
22+
## Update the client secret URL
23+
24+
On the Azure portal workbench resource page, you can update the authentication URLs for the new client secrets linked to the original app registration.
25+
26+
1. In the Azure portal, navigate to the Modeling and Simulation Workbenches (preview) page.
27+
28+
1. Select **Auth URL**.
29+
30+
![Screenshot of the Azure portal pane where the authentication URL can be updated.](./media/refresh-remote-connection-keys/auth-url.png)
31+
32+
1. Enter in the new client secret URL.
33+
34+
![Screenshot of the Azure portal pane where a new client secret URL can be entered.](./media/refresh-remote-connection-keys/client-secret-url.png)
35+
36+
These actions can only be performed by the Workbench Owner, and allow rotation of Client ID/secrets on deployed workbenches prior to expiration, which ensures business continuity for the engineering team.
37+
38+
> [!NOTE]
39+
> Please restart the connector before attempting to make a remote connection with the updated authentication URLs

articles/modeling-simulation-workbench/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,8 @@ items:
6363
href: ./how-to-guide-register-resource-provider.md
6464
- name: Create a chamber
6565
href: ./how-to-guide-chamber.md
66+
- name: Refresh remote connection keys
67+
href: ./refresh-remote-connection-keys.md
6668
- name: Resources
6769
items:
6870
- name: Troubleshoot

0 commit comments

Comments
 (0)