Skip to content

Commit 2f7fa0e

Browse files
ttorblettorble
authored
Merge pull request #246788 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 7/31
2 parents 6c8ca98 + 8dd1dce commit 2f7fa0e

File tree

62 files changed

+1047
-454
lines changed

Some content is hidden

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

62 files changed

+1047
-454
lines changed

‎articles/active-directory/saas-apps/acoustic-connect-tutorial.md

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
---
2+
title: Azure Active Directory SSO integration with Acoustic Connect
3+
description: Learn how to configure single sign-on between Azure Active Directory and Acoustic Connect.
4+
services: active-directory
5+
author: jeevansd
6+
manager: CelesteDG
7+
ms.reviewer: CelesteDG
8+
ms.service: active-directory
9+
ms.subservice: saas-app-tutorial
10+
ms.workload: identity
11+
ms.topic: how-to
12+
ms.date: 07/20/2023
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Azure Active Directory SSO integration with Acoustic Connect
18+
19+
In this article, you'll learn how to integrate Acoustic Connect with Azure Active Directory (Azure AD). Acoustic Connect is platform that helps you create marketing campaigns that resonate with people, build a loyal following, and drive revenue. When you integrate Acoustic Connect with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to Acoustic Connect.
22+
* Enable your users to be automatically signed-in to Acoustic Connect with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
You'll configure and test Azure AD single sign-on for Acoustic Connect in a test environment. Acoustic Connect supports both **SP** and **IDP** initiated single sign-on and **Just In Time** user provisioning.
26+
27+
## Prerequisites
28+
29+
To integrate Azure Active Directory with Acoustic Connect, you need:
30+
31+
* An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
32+
* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
33+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
34+
* Acoustic Connect single sign-on (SSO) enabled subscription.
35+
36+
## Add application and assign a test user
37+
38+
Before you begin the process of configuring single sign-on, you need to add the Acoustic Connect application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration.
39+
40+
### Add Acoustic Connect from the Azure AD gallery
41+
42+
Add Acoustic Connect from the Azure AD application gallery to configure single sign-on with Acoustic Connect. For more information on how to add application from the gallery, see the [Quickstart: Add application from the gallery](../manage-apps/add-application-portal.md).
43+
44+
### Create and assign Azure AD test user
45+
46+
Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon.
47+
48+
Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides).
49+
50+
## Configure Azure AD SSO
51+
52+
Complete the following steps to enable Azure AD single sign-on in the Azure portal.
53+
54+
1. In the Azure portal, on the **Acoustic Connect** application integration page, find the **Manage** section and select **single sign-on**.
55+
1. On the **Select a single sign-on method** page, select **SAML**.
56+
1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings.
57+
58+
![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
59+
60+
1. On the **Basic SAML Configuration** section, perform the following steps:
61+
62+
a. In the **Identifier** textbox, type a URL using the following pattern:
63+
`https://www.okta.com/saml2/service-provider/<Acoustic_ID>`
64+
65+
b. In the **Reply URL** textbox, type a URL using the following pattern:
66+
`https://login.goacoustic.com/sso/saml2/<ID>`
67+
68+
1. Perform the following step, if you wish to configure the application in **SP** initiated mode:
69+
70+
In the **Sign on URL** textbox, type the URL:
71+
`https://login.goacoustic.com/`
72+
73+
> [!NOTE]
74+
> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [Acoustic Connect 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.
75+
76+
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.
77+
78+
![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
79+
80+
1. On the **Set up Acoustic Connect** section, copy the appropriate URL(s) based on your requirement.
81+
82+
![Screenshot shows to copy configuration appropriate U R L.](common/copy-configuration-urls.png "Attributes")
83+
84+
## Configure Acoustic Connect SSO
85+
86+
To configure single sign-on on **Acoustic Connect** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Acoustic Connect support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
87+
88+
### Create Acoustic Connect test user
89+
90+
In this section, a user called B.Simon is created in Acoustic Connect. Acoustic Connect supports just-in-time user provisioning, which is enabled by default. There's no action item for you in this section. If a user doesn't already exist in Acoustic Connect, a new one is commonly created after authentication.
91+
92+
## Test SSO
93+
94+
In this section, you test your Azure AD single sign-on configuration with following options.
95+
96+
#### SP initiated:
97+
98+
* Click on **Test this application** in Azure portal. This will redirect to Acoustic Connect Sign-on URL where you can initiate the login flow.
99+
100+
* Go to Acoustic Connect Sign-on URL directly and initiate the login flow from there.
101+
102+
#### IDP initiated:
103+
104+
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Acoustic Connect for which you set up the SSO.
105+
106+
You can also use Microsoft My Apps to test the application in any mode. When you click the Acoustic Connect tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Acoustic Connect for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
107+
108+
## Additional resources
109+
110+
* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
111+
* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
112+
113+
## Next steps
114+
115+
Once you configure Acoustic Connect 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/cloudbees-ci-tutorial.md

Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
---
2+
title: Azure Active Directory SSO integration with CloudBees CI
3+
description: Learn how to configure single sign-on between Azure Active Directory and CloudBees CI.
4+
services: active-directory
5+
author: jeevansd
6+
manager: CelesteDG
7+
ms.reviewer: CelesteDG
8+
ms.service: active-directory
9+
ms.subservice: saas-app-tutorial
10+
ms.workload: identity
11+
ms.topic: how-to
12+
ms.date: 07/21/2023
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Azure Active Directory SSO integration with CloudBees CI
18+
19+
In this article, you'll learn how to integrate CloudBees CI with Azure Active Directory (Azure AD). Centralize management, ensure compliance, and automate at scale with CloudBees CI - the secure, scalable, and flexible CI solution based on Jenkins. When you integrate CloudBees CI with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to CloudBees CI.
22+
* Enable your users to be automatically signed-in to CloudBees CI with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
You'll configure and test Azure AD single sign-on for CloudBees CI in a test environment. CloudBees CI supports only **SP** initiated single sign-on.
26+
27+
## Prerequisites
28+
29+
To integrate Azure Active Directory with CloudBees CI, you need:
30+
31+
* An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
32+
* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
33+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
34+
* CloudBees CI single sign-on (SSO) enabled subscription.
35+
36+
## Add application and assign a test user
37+
38+
Before you begin the process of configuring single sign-on, you need to add the CloudBees CI application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration.
39+
40+
### Add CloudBees CI from the Azure AD gallery
41+
42+
Add CloudBees CI from the Azure AD application gallery to configure single sign-on with CloudBees CI. For more information on how to add application from the gallery, see the [Quickstart: Add application from the gallery](../manage-apps/add-application-portal.md).
43+
44+
### Create and assign Azure AD test user
45+
46+
Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon.
47+
48+
Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides).
49+
50+
## Configure Azure AD SSO
51+
52+
Complete the following steps to enable Azure AD single sign-on in the Azure portal.
53+
54+
1. In the Azure portal, on the **CloudBees CI** application integration page, find the **Manage** section and select **single sign-on**.
55+
1. On the **Select a single sign-on method** page, select **SAML**.
56+
1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings.
57+
58+
![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
59+
60+
1. On the **Basic SAML Configuration** section, perform the following steps:
61+
62+
a. In the **Identifier** textbox, type a value using the following pattern:
63+
`<Customer_EntityID>`
64+
65+
b. In the **Reply URL** textbox, type a URL using one of the following patterns:
66+
67+
| **Reply URL** |
68+
|------------|
69+
| `https://<CustomerDomain>/cjoc/securityRealm/finishLogin` |
70+
| `https://<CustomerDomain>/<Environment>/securityRealm/finishLogin` |
71+
| `https://cjoc.<CustomerDomain>/securityRealm/finishLogin` |
72+
| `https://<Environment>.<CustomerDomain>/securityRealm/finishLogin` |
73+
74+
1. Perform the following step, if you wish to configure the application in **SP** initiated mode:
75+
76+
In the **Sign on URL** textbox, type the URL using one of the following patterns:
77+
78+
| **Sign on URL** |
79+
|------------|
80+
| `https://<CustomerDomain>/cjoc` |
81+
| `https://<CustomerDomain>/<Environment>` |
82+
| `https://cjoc.<CustomerDomain>` |
83+
| `https://<Environment>.<CustomerDomain>` |
84+
85+
> [!NOTE]
86+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [CloudBees CI 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.
87+
88+
1. CloudBees CI 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.
89+
90+
![Screenshot shows the image of attributes configuration.](common/default-attributes.png "Image")
91+
92+
1. In addition to above, CloudBees CI application expects few more attributes to be passed back in SAML response, which are shown below. These attributes are also pre populated but you can review them as per your requirements.
93+
94+
| Name | Source Attribute|
95+
| ---------------| --------- |
96+
| email | user.mail |
97+
| username | user.userprincipalname |
98+
| displayname | user.givenname |
99+
| groups | user.groups |
100+
101+
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.
102+
103+
![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
104+
105+
1. On the **Set up CloudBees CI** section, copy the appropriate URL(s) based on your requirement.
106+
107+
![Screenshot shows to copy configuration appropriate U R L.](common/copy-configuration-urls.png "Attributes")
108+
109+
## Configure CloudBees CI SSO
110+
111+
To configure single sign-on on **CloudBees CI** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [CloudBees CI support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
112+
113+
### Create CloudBees CI test user
114+
115+
In this section, you create a user called Britta Simon at CloudBees CI SSO. Work with [CloudBees CI support team](mailto:[email protected]) to add the users in the CloudBees CI SSO platform. Users must be created and activated before you use single sign-on.
116+
117+
## Test SSO
118+
119+
In this section, you test your Azure AD single sign-on configuration with following options.
120+
121+
* Click on **Test this application** in Azure portal. This will redirect to CloudBees CI Sign-on URL where you can initiate the login flow.
122+
123+
* Go to CloudBees CI Sign-on URL directly and initiate the login flow from there.
124+
125+
* You can use Microsoft My Apps. When you click the CloudBees CI tile in the My Apps, this will redirect to CloudBees CI Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
126+
127+
## Additional resources
128+
129+
* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
130+
* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
131+
132+
## Next steps
133+
134+
Once you configure CloudBees CI 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).

0 commit comments

Comments
 (0)