Merge branch 'main' into front-door-logs

Author: johndowns

articles/active-directory-b2c/page-layout.md

@@ -59,6 +59,35 @@ Azure AD B2C page layout uses the following versions of the [jQuery library](htt
 
 ## Self-asserted page (selfasserted)
 
+**2.1.20**
+- Fixed an XSS issue on input from textbox
+
+**2.1.19**
+- Fixed accessibility bugs
+- Handle Undefined Error message for existing user sign up
+- Move Password Mismatch Error to Inline instead of Page Level
+- Accessibility changes related to High Contrast button display and anchor focus improvements
+
+**2.1.18**
+- Add asterisk for required fields
+- TOTP Store Icons position fixes for Classic Template
+- Activate input items only when verification code is verified
+- Add Alt Text for Background Image
+- Added customization for server errors by TOTP verification
+
+**2.1.17**
+- Add descriptive error message and fixed forgotPassword link
+- Make checkbox as group
+- Enforce Validation Error Update on control change and enable continue on email verified
+- Added additional field to error code to validation failure response
+	
+**2.1.16**
+- Fixed "Claims for verification control have not been verified" bug while verifying code.
+- Hide error message on validation succeeds and send code to verify
+
+**2.1.15**
+- Fixed QR code generation bug due to QR text length
+
 **2.1.14**
 - Fixed WCAG 2.1 accessibility bug for the TOTP multifactor authentication screens.
 
@@ -158,6 +187,12 @@ Azure AD B2C page layout uses the following versions of the [jQuery library](htt
 > [!TIP]
 > If you localize your page to support multiple locales, or languages in a user flow. The [localization IDs](localization-string-ids.md) article provides the list of localization IDs that you can use for the page version you select.
 
+**2.1.9**
+- Fix accessibility bugs
+- Accessibility changes related to High Contrast button display and anchor focus improvements
+	
+**2.1.8**
+- Add descriptive error message and fixed forgotPassword link!
 
 **2.1.7**
 

articles/active-directory/devices/troubleshoot-mac-sso-extension-plugin.md

@@ -93,8 +93,8 @@ Work with your MDM administrator (or Device Management team) to ensure that the
 
 The following table provides specific MDM installation guidance depending on which OS you're deploying the extension to:
 
-- [**iOS/iPadOS**: Deploy the Microsoft Enterprise SSO plug-in](/mem/intune/configuration/use-enterprise-sso-plug-in-macos-with-intune)
-- [**macOS**: Deploy the Microsoft Enterprise SSO plug-in](/mem/intune/configuration/use-enterprise-sso-plug-in-ios-ipados-with-intune)
+- [**iOS/iPadOS**: Deploy the Microsoft Enterprise SSO plug-in](/mem/intune/configuration/use-enterprise-sso-plug-in-ios-ipados-with-intune)
+- [**macOS**: Deploy the Microsoft Enterprise SSO plug-in](/mem/intune/configuration/use-enterprise-sso-plug-in-macos-with-intune)
 
 > [!IMPORTANT]
 > Although, any MDM is supported for deploying the SSO Extension, many organizations implement [**device-based conditional access polices**](../conditional-access/concept-conditional-access-grant.md#require-device-to-be-marked-as-compliant) by way of evaluating MDM compliance policies. If a third-party MDM is being used, ensure that the MDM vendor supports [**Intune Partner Compliance**](/mem/intune/protect/device-compliance-partners) if you would like to use device-based Conditional Access policies. When the SSO Extension is deployed via Intune or an MDM provider that supports Intune Partner Compliance, the extension can pass the device certificate to Azure AD so that device authentication can be completed.   

articles/active-directory/hybrid/how-to-connect-pta-quick-start.md

@@ -99,7 +99,7 @@ If you have already installed Azure AD Connect by using the [express installatio
 
 Follow these instructions to verify that you have enabled Pass-through Authentication correctly:
 
-1. Sign in to the [Azure Active Directory admin center](https://aad.portal.azure.com) with the Hybrid Identity Administratoristrator credentials for your tenant.
+1. Sign in to the [Azure Active Directory admin center](https://aad.portal.azure.com) with the Hybrid Identity Administrator credentials for your tenant.
 2. Select **Azure Active Directory** in the left pane.
 3. Select **Azure AD Connect**.
 4. Verify that the **Pass-through authentication** feature appears as **Enabled**.

articles/active-directory/saas-apps/alertops-tutorial.md

@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Azure Active Directory integration with AlertOps | Microsoft Docs'
+title: 'Tutorial: Azure AD SSO integration with AlertOps'
 description: Learn how to configure single sign-on between Azure Active Directory and AlertOps.
 services: active-directory
 author: jeevansd
@@ -9,11 +9,11 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 02/07/2023
 ms.author: jeedes
 ---
 
-# Tutorial: Integrate AlertOps with Azure Active Directory
+# Tutorial: Azure AD SSO integration with AlertOps
 
 In this tutorial, you'll learn how to integrate AlertOps with Azure Active Directory (Azure AD). When you integrate AlertOps with Azure AD, you can:
 
@@ -73,18 +73,16 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, perform the following steps:
 
     1. In the **Identifier** text box, type a URL using the following pattern:
-    `https://<SUBDOMAIN>.alertops.com`
+    `https://app.alertops.com/<SUBDOMAIN>`
 
     1. In the **Reply URL** text box, type a URL using the following pattern:
-    `https://<SUBDOMAIN>.alertops.com/login.aspx`
+    `https://api.alertops.com/api/v2/saml/<SUBDOMAIN>`
 
-1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
-
-    In the **Sign-on URL** text box, type a URL using the following pattern:
-    `https://<SUBDOMAIN>.alertops.com/login.aspx`
+    1. In the **Logout Url (Optional)** text box, type a URL using the following pattern:
+    `https://app.alertops.com/<SUBDOMAIN>`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [AlertOps Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+	> These values are not real. Update these values with the actual Identifier, Reply URL and Logout Url. Contact [AlertOps Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 1. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
 
@@ -130,33 +128,35 @@ In this section, you'll enable Britta Simon to use Azure single sign-on by grant
 
 3. If you want to setup AlertOps manually, open a new web browser window and sign into your AlertOps company site as an administrator and perform the following steps:
 
-4. Click on the **Account settings** from the left navigation panel.
+4. Click on the **Account settings** from the user profile.
 
     ![Screenshot shows the AlertOps menu with Account Settings called out.](./media/alertops-tutorial/settings.png)
 
-5. On the **Subscription Settings** page select **SSO** and perform the following steps:
+5. On the **Account Settings** page, click **Update SSO** and select **Use single sign-on (SSO)** 
 
-    ![Screenshot shows the Subscription Settings window for S S O with values entered as described in this step.](./media/alertops-tutorial/configuration.png)
+    ![Screenshot shows the Subscription Settings window for update sso as described in this step.](./media/alertops-tutorial/update-sso.png)
 
-    a. Select **Use Single Sign-On(SSO)** checkbox.
+1. In **SSO** section, perform the following steps:
 
-    b. Select **Azure Active Directory** as an **SSO Provider** from the dropdown.
+    ![Screenshot shows the Subscription Settings window for S S O with values entered as described in this step.](./media/alertops-tutorial/configuration.png)
 
-    c. In the **Issuer URL** textbox, use the identifier value, which you have used in the **Basic SAML Configuration** section in the Azure portal.
+    a. In the **Issuer URL** textbox, use the identifier value, which you have used in the **Basic SAML Configuration** section in the Azure portal.
 
-    d. In the **SAML endpoint URL** textbox, paste the **Login URL** value, which you have copied from the Azure portal.
+    b. In the **SAML endpoint URL** textbox, paste the **Login URL** value, which you have copied from the Azure portal.
 
-    e. In the **SLO endpoint URL** textbox, paste the **Login URL** value, which you have copied from the Azure portal.
+    c. In the **SLO endpoint URL** textbox, paste the **Login URL** value, which you have copied from the Azure portal.
 
-    f. Select **SHA256** as a **SAML Signature Algorithm** from the dropdown.
+    d. Select **SHA256** as a **SAML Signature Algorithm** from the dropdown.
 
-    g. Open your downloaded Certificate(Base64) file in Notepad. Copy the content of it into your clipboard, and then paste it to the X.509 Certificate text box.
+    e. Open your downloaded **Certificate(Base64)** file in Notepad. Copy the content of it into your clipboard, and then paste it to the **X.509 Certificate** text box.
+
+    f.	Enable **Allow username/password login**.
 
 ### Create AlertOps test user
 
 1. In a different browser window, sign in to your AlertOps company site as administrator.
 
-2. Click on the **Users** from the left navigation panel.
+2. Click on the **Configuration** and then **Users** from navigation panel.
 
     ![Screenshot shows the AlertOps menu with Users called out.](./media/alertops-tutorial/user.png)
 
@@ -168,19 +168,17 @@ In this section, you'll enable Britta Simon to use Azure single sign-on by grant
 
     ![Screenshot shows the Add Users pane with values entered as described in this step.](./media/alertops-tutorial/add-values.png)
 
-    a. In the **Login User Name** textbox, enter the user name of the user like **Brittasimon**.
-
-    b. In the **Official Email** textbox, enter the email address of the user like **Brittasimon\@contoso.com**.
+    a. In the **User Name** textbox, enter the user name of the user like **Brittasimon**.
 
-    c. In the **First Name** textbox, enter the first name of user like **Britta**.
+    b. In the **First Name** textbox, enter the first name of user like **Britta**.
 
-    d. In the **Last Name** textbox, enter the first name of user like **Simon**.
+    c. In the **Last Name** textbox, enter the first name of user like **Simon**.
 
-    e. Select the **Type** value from the dropdown as per your organization.
+    d. In the **Email** textbox, enter the email address of the user like `[email protected]`.
 
-    f. Select the **Role** of the user from the dropdown as per your organization.
+    f. Select the **User Role** of the user from the dropdown as per your organization.
 
-    g. Select **Add**.
+    g. Select **Submit**.
 
 ## Test SSO