Skip to content

Latest commit

 

History

History
98 lines (69 loc) · 2.62 KB

README.md

File metadata and controls

98 lines (69 loc) · 2.62 KB
Raw

DevOps Pipeline

This example shows how to create a CI/CD pipeline for IEF policies using Azure DevOps.

Scenario

The folder structure of the B2C policies normally doesn't follow a dependency tree and is mainly based on the name of the file. This makes it hard to create a simple bash or pwsh script to upload the policies in the correct order.

This tool makes it easier for B2C policies to be uploaded in-order based on the inheritance of a policy. Uploads are also faster because policies are uploaded by batch depending on its position on the inheritance tree.

src/
├─ social/
│  ├─ base.xml (1A_SBASE)
│  ├─ signupsignin.xml (1A_SSS)
├─ local/
│  ├─ base.xml (1A_LBASE)
│  ├─ signupsignin.xml (1A_LSS)
│  ├─ passwordreset.xml (1A_LPR)
├─ base.xml (1A_BASE)
├─ extension.xml (1A_EXT)

The example folder structure above has the following inheritance tree.

                1A_BASE
                    |
                 1A_EXT
                /      \
          1A_LBASE    1A_SBASE
           /    \        \      
       1A_LSS  1A_LPR    1A_SSS

These policies are then batched by their hierarchy in the tree, as well as their parent policy. The order of upload would then be.

  1. 1A_Base
  2. 1A_EXT
  3. 1A_LBASE, 1A_SBASE
  4. 1A_LSS, 1A_LPR
  5. 1A_LSSS


Local Deployment

To deploy locally, you need to install the cli tool.

Via curl

curl https://raw.githubusercontent.com/judedaryl/go-ieftool/main/install.sh | bash

Download the binary

The binaries are available in github go-ieftool

Select the binary for your system. Available binaries:

  • darwin-amd64 ( macOS intel chip )
  • darwin-arm64 ( macOS m1 chip )
  • linux-amd64 ( linux x64 )
  • windows-amd64 ( windows x64 )

Then deploy

export B2C_TENANT_ID=__TENANT_ID__
export B2C_CLIENT_ID=__CLIENT_ID__
export B2C_CLIENT_SECRET=__CLIENT_SECRET__

ieftool deploy ./policy
Usage:
  ieftool deploy [path to policies]

Required Environment Variables

variable description
B2C_TENANT_ID The B2C tenant, this can either be the tenantId (guid) or the tenant name (mytenant.onmicrosoft.com)
B2C_CLIENT_ID The client id of an app registration in B2C that has permissions for TrustFrameworkPolicies
B2C_CLIENT_SECRET The client secret of an app registration in B2C that has permissions for TrustFrameworkPolicies


Notes

This sample policy is based on LocalAccounts starter pack.