Skip to content

Commit 2408398

Browse files
authored
Merge branch 'MicrosoftDocs:main' into vameru/updating-linespacing-examples
2 parents 92c0070 + d5f44d0 commit 2408398

File tree

86 files changed

+724
-362
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

86 files changed

+724
-362
lines changed

articles/active-directory/manage-apps/application-management-certs-faq.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.workload: identity
1010
ms.topic: reference
11-
ms.date: 03/19/2021
11+
ms.date: 03/03/2023
1212
ms.author: jomondi
1313
ms.reviewer: sureshja, saumadan
1414
---
@@ -48,6 +48,13 @@ The owner of the application or Global Administrator or Application Administrato
4848

4949
In Azure AD, you can set up certificate signing options and the certificate signing algorithm. To learn more, see [Advanced SAML token certificate signing options for Azure AD apps](certificate-signing-options.md).
5050

51+
## What type of certificate can I use for configuring the SAML Certificate for single sign-on?
52+
53+
The recommendation for the SAML single sign-on certificate depends on your organization's security requirements and policies.
54+
If your organization has an internal certificate authority (PKI), using a certificate from the internal PKI can provide a higher level of security and trust. This is because the internal PKI is under the control of your organization and can be managed and monitored to ensure the security of the certificate.
55+
56+
On the other hand, if your organization doesn't have an internal certificate authority, using a certificate from an external certificate authority such as DigiCert can provide a higher level of trust and security. This is because external certificate authorities are trusted by many organizations and are subject to strict security and validation requirements.
57+
5158
## I need to replace the certificate for Azure AD Application Proxy applications and need more instructions
5259

5360
To replace certificates for Azure AD Application Proxy applications, see [PowerShell sample - Replace certificate in Application Proxy apps](../app-proxy/scripts/powershell-get-custom-domain-replace-cert.md).

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 02/16/2023
12+
ms.date: 03/10/2023
1313
ms.author: jeedes
1414

1515
---
@@ -77,7 +77,7 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
7777
`https://www.leandna.com/application/sso.html`
7878

7979
> [!Note]
80-
> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [LeanDNA Client support team](mailto:it@leandna.com) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
80+
> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [LeanDNA Client support team](mailto:support@leandna.com) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
8181
8282
1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
8383

@@ -89,11 +89,11 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
8989

9090
## Configure LeanDNA SSO
9191

92-
To configure single sign-on on **LeanDNA** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [LeanDNA support team](mailto:it@leandna.com). They set this setting to have the SAML SSO connection set properly on both sides.
92+
To configure single sign-on on **LeanDNA** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [LeanDNA support team](mailto:support@leandna.com). They set this setting to have the SAML SSO connection set properly on both sides.
9393

9494
### Create LeanDNA test user
9595

96-
In this section, you create a user called Britta Simon at LeanDNA. Work with [LeanDNA support team](mailto:it@leandna.com) to add the users in the LeanDNA platform. Users must be created and activated before you use single sign-on.
96+
In this section, you create a user called Britta Simon at LeanDNA. Work with [LeanDNA support team](mailto:support@leandna.com) to add the users in the LeanDNA platform. Users must be created and activated before you use single sign-on.
9797

9898
## Test SSO
9999

126 KB
Loading
27.7 KB
Loading
-25 Bytes
Loading
-40 Bytes
Loading
36.1 KB
Loading
3.81 KB
Loading
7.65 KB
Loading
114 KB
Loading

0 commit comments

Comments
 (0)