![]() ![]() Configures a firewall rule to open the SQL Server TCP port (default 1433).Enables the TCP/IP protocol for SQL Server.The portal automatically does the following steps: ![]() If you want to connect to your SQL Server database engine from the internet, select Public for the SQL connectivity type in the portal during provisioning. The following sections explain the Public and Private options in more detail. Your options for connectivity include: OptionĬonnect to SQL Server in the same virtual network.Ĭonnect to SQL Server locally on the same virtual machine. If you provision a SQL Server VM in the Azure portal, you have the option of specifying the type of SQL connectivity. The way a client connects to a SQL Server VM differs depending on the location of the client and the networking configuration. If you would rather have a full walkthrough of both provisioning and connectivity, see Provision a SQL Server virtual machine on Azure. If you need to troubleshoot or configure connectivity outside of the portal, see the manual configuration at the end of this topic. It covers some general connectivity scenarios and then provides steps in the portal for changing connectivity settings. Log out of Marketing Cloud, and log back in to see your app in the AppExchange menu in Marketing Cloud.įor your app to load in the Marketing Cloud iframe, ensure that your app’s x-frame-options allow the domain.This article describes how to connect to your SQL on Azure virtual machine (VM). When the user logs out of Marketing Cloud, the app session also ends. This logout URL ends the user’s session and unsets the cookie set on login. Logout - Marketing Cloud performs a GET on the logout endpoint from the browser.The redirect endpoint is returned in the JWT payload, but Marketing Cloud doesn’t do anything with it. Redirect – (Legacy packages only) A redirect is required as another endpoint that you can use to provide app information.Legacy packages only: Marketing Cloud posts the JWT here. To retrieve information about the end user, ensure that your externally hosted app immediately kicks off Marketing Cloud’s OAuth 2.0 authorization code flow and then calls the v2/userinfo route after calling your login endpoint. Login – Marketing Cloud uses this endpoint to iframe your externally hosted app. ![]() Point to localhost or test locations first, if needed, and edit these values later. The decoded JWT includes a refreshToken only if your package has an API Integration component.Įnter your app’s login, redirect, and logout URLs. (Legacy packages only) Check your SSO Claim Version. Use that access token to request information about the end user by calling the v2/userinfo REST endpoint.Ĭreate an installed package, or navigate to an existing package.Įnter a name and description for your app. Instead, your externally hosted app must use a web app or public app OAuth 2.0 integration to acquire an access token. ![]() After you know the hosted endpoint for your app, you must register the endpoint in a Marketing Cloud installed package.Īn enhanced package doesn’t use a posted JWT. You launch an app via the Marketing Cloud app menu.įor a legacy package, Marketing Cloud posts a JSON Web Token (JWT) to your externally hosted app so that it can acquire access tokens on behalf of logged-in users. Marketing Cloud apps include custom apps built by your organization or apps installed from AppExchange. All new packages are enhanced packages.Ī Marketing Cloud app is an externally hosted app that is iframed into Marketing Cloud. As of August 1, 2019, Marketing Cloud has removed the ability to create legacy packages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |