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
Copy file name to clipboardExpand all lines: docs/MicrosoftAuth.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
3
3
Authenticating with Microsoft is fully supported by Helios Launcher.
4
4
5
-
## Acquiring an Azure Client ID
5
+
## Acquiring an Entra Client ID
6
6
7
7
1. Navigate to https://portal.azure.com
8
-
2. In the search bar, search for **Azure Active Directory**.
9
-
3. In Azure Active Directory, go to **App Registrations** on the left pane (Under *Manage*).
8
+
2. In the search bar, search for **Microsoft Entra ID**.
9
+
3. In Microsoft Entra ID, go to **App Registrations** on the left pane (Under *Manage*).
10
10
4. Click **New Registration**.
11
11
- Set **Name** to be your launcher's name.
12
-
- Set **Supported account types** to *Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)*
12
+
- Set **Supported account types** to *Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)*
13
13
- Leave **Redirect URI** blank.
14
14
- Register the application.
15
15
5. You should be on the application's management page. If not, Navigate back to **App Registrations**. Select the application you just registered.
@@ -18,7 +18,7 @@ Authenticating with Microsoft is fully supported by Helios Launcher.
18
18
- Select **Mobile and desktop applications**.
19
19
- Choose `https://login.microsoftonline.com/common/oauth2/nativeclient` as the **Redirect URI**.
20
20
- Select **Configure** to finish adding the platform.
21
-
8. Go to **Credentials & secrets**.
21
+
8. Go to **Certificates & secrets**.
22
22
- Select **Client secrets**.
23
23
- Click **New client secret**.
24
24
- Set a description.
@@ -28,11 +28,11 @@ Authenticating with Microsoft is fully supported by Helios Launcher.
28
28
9. Copy **Application (client) ID**.
29
29
30
30
31
-
## Adding the Azure Client ID to Helios Launcher.
31
+
## Adding the Entra Client ID to Helios Launcher.
32
32
33
33
In `app/assets/js/ipcconstants.js` you'll find **`AZURE_CLIENT_ID`**. Set it to your application's id.
34
34
35
-
Note: Azure Client ID is NOT a secret value and **can** be stored in git. Reference: https://stackoverflow.com/questions/57306964/are-azure-active-directorys-tenantid-and-clientid-considered-secrets
35
+
Note: Entra Client ID is NOT a secret value and **can** be stored in git. Reference: https://stackoverflow.com/questions/57306964/are-azure-active-directorys-tenantid-and-clientid-considered-secrets
36
36
37
37
Then relaunch your app, and login. You'll be greeted with an error message, because the app isn't whitelisted yet. Microsoft needs some activity on the app before whitelisting it. __Trying to log in before requesting whitelist is mandatory.__
38
38
@@ -49,4 +49,4 @@ You can now authenticate with Microsoft through the launcher.
0 commit comments