Skip to content

Commit ed811b9

Browse files
authored
Merge pull request #202810 from atikmapari/Broken-link-jeedes
Broken link has been removed
2 parents 47f401b + bba3a9c commit ed811b9

File tree

3 files changed

+9
-12
lines changed

3 files changed

+9
-12
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8181
`https://<customer>.competencyiq.com/`
8282

8383
> [!NOTE]
84-
> The Sign on URL value is not real. Update the value with the actual Sign on URL. Contact [CompetencyIQ Client support team](https://www.competencyiq.com/) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
84+
> The Sign on URL value is not real. Update the value with the actual Sign on URL. Contact CompetencyIQ Client support team to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
8585
8686
5. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Federation Metadata XML** from the given options as per your requirement and save it on your computer.
8787

@@ -117,11 +117,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
117117

118118
## Configure CompetencyIQ SSO
119119

120-
To configure single sign-on on **CompetencyIQ** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [CompetencyIQ support team](https://www.competencyiq.com/). They set this setting to have the SAML SSO connection set properly on both sides.
120+
To configure single sign-on on **CompetencyIQ** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to CompetencyIQ support team. They set this setting to have the SAML SSO connection set properly on both sides.
121121

122122
### Create CompetencyIQ test user
123123

124-
In this section, you create a user called Britta Simon in CompetencyIQ. Work with [CompetencyIQ support team](https://www.competencyiq.com/) to add the users in the CompetencyIQ platform. Users must be created and activated before you use single sign-on.
124+
In this section, you create a user called Britta Simon in CompetencyIQ. Work with CompetencyIQ support team to add the users in the CompetencyIQ platform. Users must be created and activated before you use single sign-on.
125125

126126
## Test SSO
127127

@@ -135,4 +135,4 @@ In this section, you test your Azure AD single sign-on configuration with follow
135135

136136
## Next steps
137137

138-
Once you configure CompetencyIQ you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-aad).
138+
Once you configure CompetencyIQ you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-aad).

articles/active-directory/saas-apps/spring-cm-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
137137
To enable Azure Active Directory users to sign in to SpringCM, they must be provisioned into SpringCM. In the case of SpringCM, provisioning is a manual task.
138138

139139
> [!NOTE]
140-
> For more information, see [Create and Edit a SpringCM User](http://community.springcm.com/s/article/Create-and-Edit-a-SpringCM-User-1619481053).
140+
> For more information, see [Create and Edit a SpringCM User](https://support.docusign.com/s/document-item?language=en_US&bundleId=fsk1642969066834&topicId=ynn1576609925288.html&_LANG=enus).
141141
142142
**To provision a user account to SpringCM, perform the following steps:**
143143

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

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8282
`https://versal.com/sso/saml/orgs/<organization_id>`
8383

8484
> [!NOTE]
85-
> The Reply URL value is not real. Update this value with the actual Reply URL. Contact [Versal Client support team](https://support.versal.com/hc/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
85+
> The Reply URL value is not real. Update this value with the actual Reply URL. Contact Versal Client support team to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
8686

8787
1. Versal application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes, where as **nameidentifier** is mapped with **user.userprincipalname**. Versal application expects **nameidentifier** to be mapped with **user.mail**, so you need to edit the attribute mapping by clicking on **Edit** icon and change the attribute mapping.
8888

@@ -122,22 +122,19 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
122122

123123
## Configure Versal SSO
124124

125-
To configure single sign-on on **Versal** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Versal support team](https://support.versal.com/hc/). They set this setting to have the SAML SSO connection set properly on both sides.
125+
To configure single sign-on on **Versal** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to Versal support team. They set this setting to have the SAML SSO connection set properly on both sides.
126126

127127
### Create Versal test user
128128

129-
In this section, you create a user called B.Simon in Versal. Follow the [Creating a SAML test user](https://support.versal.com/hc/articles/115011672887-Creating-a-SAML-test-user)
130-
support guide to create the user B.Simon within your organization. Users must be created and activated in Versal before you use single sign-on.
129+
In this section, you create a user called B.Simon in Versal. Follow the Creating a SAML test user support guide to create the user B.Simon within your organization. Users must be created and activated in Versal before you use single sign-on.
131130

132131
## Test SSO
133132

134133
In this section, you test your Azure AD single sign-on configuration using a Versal course embedded within your website.
135-
Please see the [Embedding Organizational Courses](https://support.versal.com/hc/articles/203271866-Embedding-organizational-courses) **SAML Single Sign-On**
134+
Please see the Embedding Organizational Courses **SAML Single Sign-On**
136135
support guide for instructions on how to embed a Versal course with support for Azure AD single sign-on.
137136

138137
You will need to create a course, share it with your organization, and publish it in order to test course embedding.
139-
Please see [Creating a course](https://support.versal.com/hc/articles/203722528-Create-a-course), [Publishing a course](https://support.versal.com/hc/articles/203753398-Publishing-a-course),
140-
and [Course and learner management](https://support.versal.com/hc/articles/206029467-Course-and-learner-management) for more information.
141138

142139
## Next steps
143140

0 commit comments

Comments
 (0)