Skip to end of banner
Go to start of banner

Teams Dynamic OAuth2 Account

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

In this article

Overview

You can use this account type to connect Teams Snaps with data sources that use dynamic OAuth2 accounts.

Expression-enabled authentication fields, such as Username, Password, and Client Secret, support Secrets Management, a SnapLogic add-on that allows you to store endpoint credentials in a third-party secrets manager, such as AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. During validation and execution, pipelines obtain the credentials directly from the secrets manager. Learn more: Configure Accounts to use secrets.

Prerequisites

A registered application in the Microsoft Azure Portal with appropriate permissions can be used to generate the Access token. See Application Configuration in Azure Portal for OAuth2 Account for the steps to duly configure a registered application and for information needed to define settings for the OAuth2 account.

Limitations and Known Issues

None.

Account Settings

  • Asterisk (*): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( (blue star) ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the field set.

  • Remove icon ((blue star)): Indicates that you can remove fields from the field set.

Field Name

Field Type

Description

Label*

Default Value: N/A
ExampleTeams Dynamic OAuth2 Account

String

Specify a unique label for the account.

Access token*

Default Value: N/A
Example: 1abcd23e45fg6789hi01-23456jk789l01abcd23e-45fg6789hi01-23456jk789l01abcd23e-45fg-6789-hi01-23456jk789l0

String/Expression

Specify the Access Token generated using the authorization code/client credentials flow. See Access Token Generation for details. 

Access Token Type*

Default ValueOn behalf of user (authorization_code grant type)
Example: On behalf of application (client_credentials grant type)

Dropdown list

Select the type of Access Token (application or individual user) you are using for the account from the two options available:

  • On behalf of user (authorization_code grant type). To run the Snaps as an individual user.

  • On behalf of application (client_credentials grant type). To run the Snaps as an (Azure portal) application.

Access Token Generation

Depending on the type of access required, the Teams Dynamic account needs either an Access Token (application) or Authorization Code (user) to connect to your Microsoft Teams instance.

  • Access Token to perform actions on behalf of an application (client_credentials grant type). See Get access without a user in Microsoft Docs for more information.

  • Authorization Code to perform actions on behalf of a signed-in user (authorization_code grant type). See Get access on behalf of a user in Microsoft Docs for more information.

Troubleshooting

None.


Related Content

  • No labels