Skip to content

Commit 9fe06e1

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into acifresh2
2 parents c5ccf67 + 279d9e1 commit 9fe06e1

File tree

5 files changed

+351
-143
lines changed

5 files changed

+351
-143
lines changed

articles/active-directory/saas-apps/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1414,6 +1414,8 @@
14141414
href: trakstar-tutorial.md
14151415
- name: Trello
14161416
href: trello-tutorial.md
1417+
- name: TripActions
1418+
href: tripactions-tutorial.md
14171419
- name: Trisotech Digital Enterprise Server
14181420
href: trisotechdigitalenterpriseserver-tutorial.md
14191421
- name: TurboRater
Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with TripActions | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and TripActions.
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: 233af4cf-7f73-4e6c-905e-5c631d87e34a
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.topic: tutorial
16+
ms.date: 01/08/2020
17+
ms.author: jeedes
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with TripActions
23+
24+
In this tutorial, you'll learn how to integrate TripActions with Azure Active Directory (Azure AD). When you integrate TripActions with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to TripActions.
27+
* Enable your users to be automatically signed-in to TripActions with their Azure AD accounts.
28+
* Manage your accounts in one central location - the Azure portal.
29+
30+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
31+
32+
## Prerequisites
33+
34+
To get started, you need the following items:
35+
36+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37+
* TripActions single sign-on (SSO) enabled subscription.
38+
39+
## Scenario description
40+
41+
In this tutorial, you configure and test Azure AD SSO in a test environment.
42+
43+
* TripActions supports **SP and IDP** initiated SSO
44+
* TripActions supports **Just In Time** user provisioning
45+
46+
## Adding TripActions from the gallery
47+
48+
To configure the integration of TripActions into Azure AD, you need to add TripActions from the gallery to your list of managed SaaS apps.
49+
50+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
51+
1. On the left navigation pane, select the **Azure Active Directory** service.
52+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
53+
1. To add new application, select **New application**.
54+
1. In the **Add from the gallery** section, type **TripActions** in the search box.
55+
1. Select **TripActions** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
56+
57+
## Configure and test Azure AD single sign-on for TripActions
58+
59+
Configure and test Azure AD SSO with TripActions using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in TripActions.
60+
61+
To configure and test Azure AD SSO with TripActions, complete the following building blocks:
62+
63+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
64+
* **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
65+
* **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
66+
1. **[Configure TripActions SSO](#configure-tripactions-sso)** - to configure the single sign-on settings on application side.
67+
* **[Create TripActions test user](#create-tripactions-test-user)** - to have a counterpart of B.Simon in TripActions that is linked to the Azure AD representation of user.
68+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
69+
70+
## Configure Azure AD SSO
71+
72+
Follow these steps to enable Azure AD SSO in the Azure portal.
73+
74+
1. In the [Azure portal](https://portal.azure.com/), on the **TripActions** application integration page, find the **Manage** section and select **single sign-on**.
75+
1. On the **Select a single sign-on method** page, select **SAML**.
76+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
77+
78+
![Edit Basic SAML Configuration](common/edit-urls.png)
79+
80+
1. On the **Basic SAML Configuration** section, the user does not have to perform any step as the app is already pre-integrated with Azure.
81+
82+
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
83+
84+
In the **Sign-on URL** text box, type the URL:
85+
`https://app.tripactions.com`
86+
87+
1. Click **Save**.
88+
89+
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.
90+
91+
![The Certificate download link](common/metadataxml.png)
92+
93+
1. On the **Set up TripActions** section, copy the appropriate URL(s) based on your requirement.
94+
95+
![Copy configuration URLs](common/copy-configuration-urls.png)
96+
97+
### Create an Azure AD test user
98+
99+
In this section, you'll create a test user in the Azure portal called B.Simon.
100+
101+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
102+
1. Select **New user** at the top of the screen.
103+
1. In the **User** properties, follow these steps:
104+
1. In the **Name** field, enter `B.Simon`.
105+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
106+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
107+
1. Click **Create**.
108+
109+
### Assign the Azure AD test user
110+
111+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to TripActions.
112+
113+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
114+
1. In the applications list, select **TripActions**.
115+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
116+
117+
![The "Users and groups" link](common/users-groups-blade.png)
118+
119+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
120+
121+
![The Add User link](common/add-assign-user.png)
122+
123+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
124+
1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
125+
1. In the **Add Assignment** dialog, click the **Assign** button.
126+
127+
## Configure TripActions SSO
128+
129+
To configure single sign-on on **TripActions** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [TripActions support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
130+
131+
### Create TripActions test user
132+
133+
In this section, a user called B.Simon is created in TripActions. TripActions supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in TripActions, a new one is created after authentication.
134+
135+
## Test SSO
136+
137+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
138+
139+
When you click the TripActions tile in the Access Panel, you should be automatically signed in to the TripActions for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
140+
141+
## Additional resources
142+
143+
- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
144+
145+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
146+
147+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
148+
149+
- [Try TripActions with Azure AD](https://aad.portal.azure.com/)

articles/event-hubs/event-hubs-messaging-exceptions.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,23 @@ The following steps may help you with troubleshooting connectivity/certificate/t
114114
```shell
115115
telnet <yournamespacename>.servicebus.windows.net 5671
116116
```
117+
118+
An example of successful message:
119+
120+
```xml
121+
<feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Publicly Listed Services</title><subtitle type="text">This is the list of publicly-listed services currently available.</subtitle><id>uuid:27fcd1e2-3a99-44b1-8f1e-3e92b52f0171;id=30</id><updated>2019-12-27T13:11:47Z</updated><generator>Service Bus 1.1</generator></feed>
122+
```
123+
124+
An example of failure error message:
125+
126+
```json
127+
<Error>
128+
<Code>400</Code>
129+
<Detail>
130+
Bad Request. To know more visit https://aka.ms/sbResourceMgrExceptions. . TrackingId:b786d4d1-cbaf-47a8-a3d1-be689cda2a98_G22, SystemTracker:NoSystemTracker, Timestamp:2019-12-27T13:12:40
131+
</Detail>
132+
</Error>
133+
```
117134
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command will try to establish 25 different TCP connections every 1 second with the service. Then, you can check how many of them succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
118135
119136
```shell

articles/virtual-machines/linux/image-builder-gallery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ manager: gwallace
1010
---
1111
# Preview: Create a Linux image and distribute it to a Shared Image Gallery
1212

13-
This article shows you how you can use the Azure Image Builder to create an image version in a [Shared Image Gallery](https://docs.microsoft.com/azure/virtual-machines/windows/shared-image-galleries), then distribute the image globally.
13+
This article shows you how you can use the Azure Image Builder, and the Azure CLI, to create an image version in a [Shared Image Gallery](https://docs.microsoft.com/azure/virtual-machines/windows/shared-image-galleries), then distribute the image globally. You can also do this using [Azure PowerShell](../windows/image-builder-gallery.md).
1414

1515

1616
We will be using a sample .json template to configure the image. The .json file we are using is here: [helloImageTemplateforSIG.json](https://github.com/danielsollondon/azvmimagebuilder/blob/master/quickquickstarts/1_Creating_a_Custom_Linux_Shared_Image_Gallery_Image/helloImageTemplateforSIG.json).

0 commit comments

Comments
 (0)