Integration Settings

Integration Settings include any settings or configuration related to FlexDeploy 3rd party integrations.

image-20241023-143230.png

OAuth Apps

OAuth applications allow FlexDeploy to seamlessly integrate with other 3rd party tools such as GitHub and Microsoft Azure. Setting up an OAuth application consists of two steps:

  1. Configuring the required application properties such as the Client Id and Client Secret.

  2. Authorizing the application - this is the process of clicking an “Authorize” or “Connect” button and being redirected to the application website and approving the use

Configuring an OAuth Application

To configure an OAuth Application, first click the Add Application button. This will present a popup where you can choose from predefined templates of OAuth Applications that FlexDeploy supports.

image-20241023-150945.png

Once you have made your selection, click the Add button. Next a form along with instructions will be presented. Follow the on screen instructions for obtaining the necessary information to complete the form.

Lastly, click the Save button. At this point the OAuth Application is ready to be authorized.

Authorizing OAuth Applications

The authorization process will vary depending upon the scope of the application. There are two main scopes of OAuth Applications that can be created in FlexDeploy: FlexDeploy scoped and User scoped.

The scope of the application is determined by the template that was chosen when creating the application.

FlexDeploy Scoped Applications

FlexDeploy Scoped OAuth apps are applications that are configured and authorized all on the Integration Settings page. Authorization only needs to be provided once and can then be used anywhere in FlexDeploy.

User Scoped Applications

Like FlexDeploy Scoped applications, User Scoped apps are configured on the Integration Settings page. However, the authorization is done by each user from their User Profile page.

OAuth Apps in Use

Each OAuth application has a “Functional Area” that determines the features the app offers. This is denoted by the tag next to the Application name.

The following list describes some of the usages for different Functional Area’s of OAuth applications.

Functional Area

Uses

Functional Area

Uses

EMAIL

  • System Settings - Email Configuration

GIT

 

The following macros are not currently supported in the footer:
  • style