Skip to content
route-service-auth-egress-buildpack
C# PowerShell Shell Batchfile
Branch: master
Clone or download
Pull request Compare This branch is 2 commits ahead of alfusinigoj:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build
scripts
src
tests/UnitTests
.gitignore
.nuke
EgressBuildpack.sln
LICENSE
README.md
build.ps1
build.sh
nuget.config

README.md

Breaking: v1.* - Use github or azure devops as source for kerberos config; Use github or azure devops or azure key vault as source for keytab files

This project offers a supply buildpack which helps applying IWA security (kerberos) for app-app/svc-svc secure communication, in PCF.

In detail, if any service running in PCF is protected by route service (https://github.com/cloudfoundry-community/kerberos-auth-route-service), the client application should be attaching a valid kerberos ticket, so as to be authenticated properly. This buildpack, together with the nuget package mentioned below will be intercepting all the egress requests and attaches a valid kerberos ticket. For more details, please listen to Andrew Stackhov's video here "youtube video link here"'

Specific functionalities executed by this buildpack

  1. Modifies the wcf client section in web.config with endpoint behaviours required for injection of kerberos ticket
  2. Adds MIT Kerberos dlls and Kerberos executables required for the operation, into application bin folder
  3. Validates if PivotalServices.WcfClient.Kerberos.Interceptor package is installed
  4. Copies the provided kerberos configuration file and keytab file from the sources (github and azure devops git repos). Configure the sources as mentioned in the Variables section below.

For kerberos config template, please here https://github.com/cloudfoundry-community/kerberos-auth-egress-wcf-client-interceptor/blob/master/src/RouteServiceIwaWcfInterceptor/krb5.ini

Environment Variables

  • Kerberos config file
    1. If you choose to use GitHub for kerberos config file, please set the following environment variable and Github Configuration Variables (below) in the application cf manifest

      • GITHUB_KERBEROS_CONFIG_FILE_RAW_URL Raw url for the kerberos config file
    2. If you choose to use Azure DevOps for kerberos config file, please set the following environment variable and Azure DevOps Configuration Variables (below) in the application cf manifest

      • AZURE_DEVOPS_SOURCE_KERBEROS_CONFIG_FILE_URL_RELATIVE_TO_THE_ROOT Path of the keytab file referring to the root of the repo
  • Kerberos keytab file
    1. If you choose to use GitHub for kerberos keytab file, please set the following environment variable and Github Configuration Variables (below) in the application cf manifest

      • GITHUB_KEYTAB_FILE_RAW_URL Raw url for the keytab file
    2. If you choose to use Azure DevOps for kerberos keytab file, please set the following environment variable and Azure DevOps Configuration Variables (below) in the application cf manifest

      • AZURE_DEVOPS_SOURCE_KEYTAB_FILE_URL_RELATIVE_TO_THE_ROOT Path of the keytab file referring to the root of the repo
    3. If you choose to use Azure Key Valut for kerberos keytab file, please set the following environment variable and Azure Key Vault Configuration Variables (below) in the application cf manifest

      • AZURE_SECRET_NM Name of the Key Vault Secret
      • AZURE_SECRET_VER Version of the Key Vault Secret

      NOTE: Secret Value should be Base64 content of the keytab file

  • Github Configuration Variables
    • GITHUB_ACCESS_TOKEN GitHub access token (if required)
  • Azure DevOps Configuration Variables
    • AZURE_DEVOPS_COLLECTION_URL (See below sample)
    • AZURE_DEVOPS_PROJECT_NAME (See below sample)
    • AZURE_DEVOPS_REPO_NAME (See below sample)
    • AZURE_DEVOPS_ACCESS_TOKEN Azure DevOps access token
    • For example if url is https://dev.visualstudio.com/my_project/_git/my_repo
      • Collection Url: https://dev.visualstudio.com
      • ProjectName: my_project
      • RepoName: my_repo
  • Azure Key Vault Configuration Variables
    • AZURE_VAULT_BASE_URL (See below sample)
    • AZURE_APP_ID Application Client Id (Used to obtain the access token)
    • AZURE_APP_SECRET Application Client Secret (Used to obtain the access token)
    • For example if url is https://mysecret.vault.azure.net/secrets/Test/12345
      • Vault Base Url: https://mysecret.vault.azure.net
      • Secret Name: Test
      • Secret Version: 12345

Dependencies

Nuget Package to be added PivotalServices.WcfClient.Kerberos.Interceptor (https://github.com/cloudfoundry-community/kerberos-auth-egress-wcf-client-interceptor)

To manually build and release this buildpack using command nuke <target> from powershell window.

Targets

  1. Clean --> cleans bin/obj/artifacts folder
  2. Restore --> Restores all nuget dependencies (depends on Clean)
  3. Compile --> Compiles the buildpack (depends on Restore)
  4. Test --> Runs all the tests for the buildpack (depends on Compile)
  5. Publish --> Publishes the buildpack artifact under artifacts directory (depends on Test)
  6. Release --> Create a new buildpack release under the github repo (depends on Publish). You will be prompted for Github ApiToken which has release rights to the github repo, alternatively you can pass as commandline param --GitHubToken
You can’t perform that action at this time.