Skip to main content


To make it simpler to access PactFlow, we've rolled out Single Sign On (SSO) authentication with Github, Google and SAML2.0.

How it works

SSO users are automatically provisioned when they first authenticate.

NOTE:   Changing these settings may require users to either do a hard refresh in their browser (CTRL-F5 on Windows and Linux, CMD-R on Mac OSX) before the next time they try login, or may require them to clear their browser cookies and cache.

GitHub Authentication

Eligible plans: all

For GitHub authentication, you need to configure the GitHub organisations that you would like users who belong to be able to log into your broker instance.

Steps to configure

  1. Navigate to the Authentication settings page, and add the names of the Github organisation(s) that should be granted access (hint: given this project URL the name should be pactflow: Make sure you get the case right, as the name will need to match exactly.
  2. Press the Save button.
  3. After configuring Github, you will need to logout.
  4. Once logged out navigate back to your login screen. You should now have a Github option.
  5. Login with the new Github option.
  6. On first authentication attempt, it will require authorization with Github. Follow the in-app prompts to guide you.

GitHub Authentication Settings


Seeing error "None of your GitHub organizations have been registered with PactFlow." when trying to log in

There are multiple reasons why this error may be shown.

You may not have clicked "Grant" or "Request" for that organization on the GitHub PactFlow Authorize screen

To fix this, log out of PactFlow, go to Revoke access to PactFlow, then log in to PactFlow again. You will be given the opportunity to grant or request access to your organization again during the login flow.

If you clicked "Request", you may need to ask an administrator to approve the authorization

To fix this, please contact your organization's GitHub administrator, and ask that they follow these instructions to approve PactFlow

You may have previously authenticated to PactFlow with GitHub, but joined the organization since doing so

To fix this, log out of PactFlow, go to Revoke access to PactFlow, then log in to PactFlow again. You will be given the opportunity to grant or request access to your organization again during the login flow.

You are not a member of any organizations

Please read for instructions on creating a GitHub Organization.

Name is not populated after signing in

  • Ensure that you have given the PactFlow application the permisson to read personal information. To check this:
  • If you have already given this permission, and you still see no name populated in PactFlow, then check that you have set a name in your public profile.
    • Go to{your-github-username} in a browser.
    • Click the Edit profile button shown underneath your avatar on the left of the page.
    • Enter a value in the Name field.
    • Open new browser window that has no cookies shared from your previous PactFlow login (clear all your cookies or use an incognito window) and log in to PactFlow again. It should take you through the GitHub login screens - if not, then it's re-using your previous session details, and you need to clear your cookies and try again.
    • Once you have successfully logged in to PactFlow again, you should see your name populated in PactFlow.

Google Authentication

Eligible plans: all

For Google authentication, you must configure one or more hosted domains of the users that will be allowed to log into your PactFlow account. On your next login, you will see an option to login with Google has been added. Any users who have a valid identity for the hosted domain will be able to login to your PactFlow instance.

For example if you use Google Workspace as your choice of email provider and your email is, the hosted domain might be

You can also use any valid Google or GMail email address, such as or This constrains the authentication to a single user.

Google Authentication Settings

SAML Support

Eligible plans: Enterprise

PactFlow has support for a SAML 2.0 integration with a compatible Identity Provider (IdP) such as Okta, Ping, Auth0, Azure AD, OneLogin etc.

SAML2.0 allows you to externalise the authentication and access to your PactFlow account. Authorization and fine grained permissions are managed within your account by an account Administrator.

Supported capabilities:

  • Authorization from an external IdP
  • Automated user provisioning into your account
  • SP initiated login

We do not current support the following:

  • Automated user deprovisioning (users will appear "active" and count toward user limits, although will not be able to login if disabled in the IdP)
  • IdP initiated login
  • Service Provider (SP) initiated logout flow


1. Configure PactFlow as a Service Provider in your IdP

In your IdP, create a new Service Provider with the following properties:

  • Audience URI (SP Entity ID): urn:amazon:cognito:sp:ap-southeast-2_x0L1olP0D
  • Single sign on URL (Reply URL):
  • Name ID format must be set to "Persistent": urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

2. Map the required SAML2.0 attributes

The following attributes are required by PactFlow and must be mapped in your IdP to be sent through during the authentication flow:

Property to map from your IDPAttribute Name in SAML AssertionName Format
First Name Reference
Last Name Reference
Email Address Reference

For example, a valid Attribute in the SAML assertion for a user's first name would look like this:

<Attribute Name="" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
<AttributeValue xmlns:xsi="" xsi:type="xs:string">Joe</AttributeValue>

3. Export IdP metadata

Once you have configured PactFlow as a Service Provider, please send your PactFlow account details and an externally accessible URL to the metadata file via our support form. If it is not possible to provide a URL, then the metadata may be exported as an XML file. It is preferable to use a URL, as this will allow you to make any updates without having to contact PactFlow support.


The following can be used to compare against your own IdP setup to check if you're missing anything. Note these were both produced via Okta.

Example valid metadata document

<?xml version="1.0" encoding="UTF-8"?>
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="">
<md:IDPSSODescriptor WantAuthnRequestsSigned="false" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
<md:KeyDescriptor use="signing">
<ds:KeyInfo xmlns:ds="">
<md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="" />
<md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="" />

This is the assertion sent to the PactFlow Reply URL

<?xml version="1.0" encoding="UTF-8"?>
<saml2p:Response xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:xs="" Destination="" ID="id3718331499099330736053153" InResponseTo="_125f72fb-e3bf-40d0-ba42-77152c2c0845" IssueInstant="2020-08-19T03:26:29.364Z" Version="2.0">
<saml2:Issuer xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"></saml2:Issuer>
<ds:Signature xmlns:ds="">
<ds:CanonicalizationMethod Algorithm="" />
<ds:SignatureMethod Algorithm="" />
<ds:Reference URI="#id3718331499099330736053153">
<ds:Transform Algorithm="" />
<ds:Transform Algorithm="">
<ec:InclusiveNamespaces xmlns:ec="" PrefixList="xs" />
<ds:DigestMethod Algorithm="" />
<ds:DigestValue>uJgujmj ... 26En8=</ds:DigestValue>
<ds:SignatureValue>S/xuVKLEfmIj2I0+Vjvr ... 29vtaSKQkHeQMwCpSUfKIIoZ/OlnDQ==</ds:SignatureValue>
<ds:X509Certificate>MIIDpDCCAoygAwIBAgIGAXPl6shZMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi04OTA1NTYxHDAaBgkqhkiG9w0BCQEW DWluZm9Ab2t0YS5jb20wHhcNMjAwODEzMDM0MjU1WhcNMzAwODEzMDM0MzU1WjCBkjELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNVBAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtODkwNTU2MRwwGgYJ KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmgdKOOa+KPUYuCXNl6ab/1AgaRIzxjvXxyEjAceLig4ljsgRVawo5F8CG2JMa2anejfJdHsu/sNoSORi59V9MSYso8mH2krRNKkAiMWwXO6ncvHxwWJsZqPnuDMPhU+vhCbxAg9zSKgnuhW/Li/qs16x IDjmJFUXMSksbC9wEmrHw1hR8Zl94L0lwcTLwVeQtTZ3pfpDN4HT84wA/lc1sn/heXyikv1fgP1EonpbsQXuFjw9vQT7UekAjeYi0cVTX0wVZ3WKob62v5zJZhFkVrdDbJ7Zsg9sGwXom3RpKcLEw/voPcSc69ARiCkHY4fhOSykkFottLh/xsTp0Pw3UQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAEoVfX 8yda3v4s/28nPpy0g+m1oXduagcYKFjCWg7Wou7G47Li8k2Xcm1Ck+gMvDn10dzHq2+RBKwBs59dmsqk2Pq8pI9C5Cp2f7Ad+or3XhpWa4IKQjVvGt1vV2WCasEPHwL+1a9Alhg47x/GmoYoMRHaT7fG+a3ZYe+QF5cIGFyWj5QxUkKcD/FE37N2DQuPQOzOHDYe9BQCi/FFC2GarpiGIgPQd9RDjsTDpFKt9lzfbF/65I6ISDB5TQyCaLvSf8cofivLe3EQpw0sZ97fLi7VOlOY888elByNALcl5rf7qLuh/gPOiv9B1SsJ0l/zk0FxwLCCKFGXn1RSV8/</ds:X509Certificate>
<saml2p:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />
<saml2:Assertion xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" ID="id37183314991817892005295917" IssueInstant="2020-08-19T03:26:29.364Z" Version="2.0">
<saml2:Issuer Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"></saml2:Issuer>
<ds:Signature xmlns:ds="">
<ds:CanonicalizationMethod Algorithm="" />
<ds:SignatureMethod Algorithm="" />
<ds:Reference URI="#id37183314991817892005295917">
<ds:Transform Algorithm="" />
<ds:Transform Algorithm="">
<ec:InclusiveNamespaces xmlns:ec="" PrefixList="xs" />
<ds:DigestMethod Algorithm="" />
<ds:DigestValue>UTRr45 ... 7drNjg2E=</ds:DigestValue>
<ds:SignatureValue>a7SSAhT+xjgmwq0d+y6 ... 3Wzt+9g3sIeOuz30MuDn+kUjqs1w==</ds:SignatureValue>
<ds:X509Certificate>MIIDpDCCAoygAwIBAgIGAXPl6shZMA0GCSqGSIb3DQEBCwUAMIGSMQswCQYDVQQGEwJVUzETMBEG A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU MBIGA1UECwwLU1NPUHJvdmlkZXIxEzARBgNVBAMMCmRldi04OTA1NTYxHDAaBgkqhkiG9w0BCQEW DWluZm9Ab2t0YS5jb20wHhcNMjAwODEzMDM0MjU1WhcNMzAwODEzMDM0MzU1WjCBkjELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExFjAUBgNVBAcMDVNhbiBGcmFuY2lzY28xDTALBgNVBAoMBE9rdGExFDASBgNVBAsMC1NTT1Byb3ZpZGVyMRMwEQYDVQQDDApkZXYtODkwNTU2MRwwGgYJ KoZIhvcNAQkBFg1pbmZvQG9rdGEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmgdKOOa+KPUYuCXNl6ab/1AgaRIzxjvXxyEjAceLig4ljsgRVawo5F8CG2JMa2anejfJdHsu/sNoSORi59V9MSYso8mH2krRNKkAiMWwXO6ncvHxwWJsZqPnuDMPhU+vhCbxAg9zSKgnuhW/Li/qs16x IDjmJFUXMSksbC9wEmrHw1hR8Zl94L0lwcTLwVeQtTZ3pfpDN4HT84wA/lc1sn/heXyikv1fgP1EonpbsQXuFjw9vQT7UekAjeYi0cVTX0wVZ3WKob62v5zJZhFkVrdDbJ7Zsg9sGwXom3RpKcLEw/voPcSc69ARiCkHY4fhOSykkFottLh/xsTp0Pw3UQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQAEoVfX8yda3v4s/28nPpy0g+m1oXduagcYKFjCWg7Wou7G47Li8k2Xcm1Ck+gMvDn10dzHq2+RBKwBs59d msqk2Pq8pI9C5Cp2f7Ad+or3XhpWa4IKQjVvGt1vV2WCasEPHwL+1a9Alhg47x/GmoYoMRHaT7fG+a3ZYe+QF5cIGFyWj5QxUkKcD/FE37N2DQuPQOzOHDYe9BQCi/FFC2GarpiGIgPQd9RDjsTDpFKCt9lzfbF/65I6ISDB5TQyCaLvSf8cofivLe3EQpw0sZ97fLi7VOlOY888elByNALcl5rf7qLuh/gPOiv9B1SsJ0l/zk0FxwLCCKFGXn1RSV8/</ds:X509Certificate>
<saml2:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"></saml2:NameID>
<saml2:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
<saml2:SubjectConfirmationData InResponseTo="_125f72fb-e3bf-40d0-ba42-77152c2c0845" NotOnOrAfter="2020-08-19T03:31:29.364Z" Recipient="" />
<saml2:Conditions NotBefore="2020-08-19T03:21:29.364Z" NotOnOrAfter="2020-08-19T03:31:29.364Z">
<saml2:AuthnStatement AuthnInstant="2020-08-19T03:26:29.364Z" SessionIndex="_125f72fb-e3bf-40d0-ba42-77152c2c0845">
<saml2:Attribute Name="" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
<saml2:AttributeValue xmlns:xsi="" xsi:type="xs:string">Joe</saml2:AttributeValue>
<saml2:Attribute Name="" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
<saml2:AttributeValue xmlns:xsi="" xsi:type="xs:string">Bloggs</saml2:AttributeValue>
<saml2:Attribute Name="" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
<saml2:AttributeValue xmlns:xsi="" xsi:type="xs:string"></saml2:AttributeValue>


See for further details on any of the steps below.

1. Create a SAML app in Okta

  1. Open the Okta Developer Console.
  2. Choose Applications, and then choose Add Application.
  3. On the Add Application page, choose Create New App.
  4. In the Create a New Application Integration dialog, confirm that Platform is set to Web.
  5. For Sign on method, choose SAML 2.0.
  6. Choose Create.

Okta create app

2. Configure SAML integration for your Okta app

  1. On the Create SAML Integration page, under General Settings, enter a name for your app.
  2. (Optional) Upload a logo and choose the visibility settings for your app.
  3. Choose Next.
  4. Under GENERAL, for Single sign on URL, enter
  5. For Audience URI (SP Entity ID), enter urn: urn:amazon:cognito:sp:ap-southeast-2_x0L1olP0D
  6. Under ATTRIBUTE STATEMENTS (OPTIONAL), add 3 statements with the following information:
    1. For Name, enter the SAML attribute name
    2. For Value, enter user.firstName.
    3. For Name, enter the SAML attribute name
    4. For Value, enter user.lastName.
    5. For Name, enter the SAML attribute name
    6. For Value, enter
  7. Choose Next.
  8. Choose a feedback response for Okta Support.
  9. Choose Finish.

Okta create app

3. Assign a user to your Okta application

  1. On the Assignments tab for your Okta app, for Assign, choose Assign to People.
  2. Next to the user that you want to assign, choose Assign.
  3. Note: If this is a new account, the only option available is to choose yourself (the admin) as the user.
  4. Choose Save and Go Back. Your user is assigned.
  5. Choose Done.

Assign user screen in Okta Assign a user in Okta

4. Get the IdP metadata for your Okta application

  1. On the Sign On tab for your Okta app, find the Identity Provider metadata hyperlink. Right-click the hyperlink, and then copy the URL.
  2. For more information, see Configure SAML in your app in the Set up a SAML application in Okta guide on the Okta Developer website.

5. Contact PactFlow to enable your IdP

Send your unique metadata URL to us here.

Azure Active Directory

See for more information.

  1. Create a non gallery application

Create a non-gallery app

  1. Follow the Microsoft documentation for creating a non gallery application.
  • Choose Non-gallery application at the Add your own app screen.
  • Set the name to pactflow when prompted.

Create a non-gallery app

  1. When the application has been created, assign the users that should be allowed to login to PactFlow.

Assign Users

  1. Once the users have been assigned, select the Single sign-on tab. Select SAML.

Configure SSO

  1. Proceed to the next step.

Configure SAML

  1. Set the Identifier (Entity ID) to urn:amazon:cognito:sp:ap-southeast-2_x0L1olP0D

  2. Set the Reply URL to

  3. Relay State and Logout Url fields blank.

  4. Set the Sign On URL to point to your unique PactFlow URL (e.g. (this is required as we don't support IDP initiated sign-on)

  5. To add user attributes, click "View and edit all other user attributes" to edit the attributes to be sent to the application in the SAML token when users sign in. Add the following 3 attributes:

    1. First Name:
    2. Last Name:
    3. Email Address:

OneLogin - via PactFlow Connector

  1. On the OneLogin portal page, choose Administration.
  2. From the Administration page, choose Applications, and then choose Add App.

Find PactFlow Connector

  1. In the search bar under Find Applications, enter "pactflow", and then choose the PactFlow Connector
  2. (Optional) Do any of the following: For Display Name, enter a name and description. For example, PactFlow. For Rectangular Icon and Square Icon, you can add icons for PactFlow. For Description, enter a short summary description.
  3. Choose Save.
  4. On the homepage for the new application, choose "More Actions > SAML Metadata" from the main menu

Configure Onelogin metadata

OneLogin - manual setup

1. Create a OneLogin application

  1. On the OneLogin portal page, choose Administration.
  2. From the Administration page, choose Applications, and then choose Add App.
  3. In the search bar under Find Applications, enter saml, and then choose SAML Test Connector (Advanced) to open the Add SAML Test Connector page.
  4. (Optional) Do any of the following: For Display Name, enter a name and description. For example, PactFlow. For Rectangular Icon and Square Icon, you can add icons for PactFlow. For Description, enter a short summary description.
  5. Choose Save.

2. Edit your OneLogin application configuration

  1. Choose Configuration.
  2. On the Configuration page, do the following: For RelayState, leave it blank. For Audience, enter urn:amazon:cognito:sp:ap-southeast-2_x0L1olP0D Leave Recipient blank. For ACS (Consumer) URL Validator, enter For ACS (Consumer) URL, enter Leave Single Logout URL blank.

3. Edit your OneLogin application's parameters

  1. Choose Parameters. Note: One parameter (NameID (fka Email)) is already listed—this is expected.
  2. Choose Add parameter to create a new, custom parameter.
  3. In the New Field dialog, for Field name, enter
  4. For Flags, select the Include in SAML assertion check box.
  5. Choose Save.
  6. For Value, choose Email from the list.
  7. Choose Save.

You then need to repeat the steps for first name and last name.

  1. Choose Add parameter to create a new, custom parameter.
  2. In the New Field dialog, for Field name, enter Firstname
  3. For Flags, select the Include in SAML assertion check box.
  4. Choose Save.
  5. For Value, choose First Name from the list.
  6. Choose Save.
  7. Choose Add parameter to create a new, custom parameter.
  8. In the New Field dialog, for Field name, enter Lastname
  9. For Flags, select the Include in SAML assertion check box.
  10. Choose Save.
  11. For Value, choose First Name from the list.
  12. Choose Save.

You should have the following attributes defined:

Onelogin Attributes

4. Copy the IdP metadata for your OneLogin application

  1. Choose SSO.
  2. Under Issuer URL, copy the URL to your clipboard. You need to provide this URL to us.
  3. Choose Save to save all your changes to your OneLogin application.


Debug SAML Assertions

The SAML login assertion request/response happens via the browser, and for security reasons, it's not something PactFlow is able to see.

You can however, extract the SAML assertion from your web browser during a login flow. For example, using most modern browsers such as Chrome perform the following steps:

  1. Open your developer tools console
  2. View the network tab and ensure "persist" or "preserve log" is enabled
  3. Head to your pactflow account: https://<youraccount>
  4. Login via your IdP until you experience the issue
  5. Find the request to
  6. Copy the value of the SAMLResponse into a tool such as to decode and view

SAML debugging


1. Name not appearing in user management screens

You are missing the mappings for "First name" and "Last Name", see Map the required SAML2.0 attributes in Setup.

2. "Invalid State/RelayState provided"

Your SAML provider has not been configured on the PactFlow side (please contact us if this is the case) or the metadata document supplied does not match your IdP.

3. "Invalid samlResponse or relayState from identity provider"

You have attempted to login via your IdP (IdP Initiated Login) which is not supported.

4. I've added an identity provider and see duplicate users

Users are identified uniquely by their identity provider. This means that a user that previously logged into PactFlow via username/password with the email "" who then authenticates via Github, will be treated as a separate user with separate permissions.

You can discriminate between the users based on the "identity provider" column in our Users UI screen. To reduce the number of users in your account, you can disable any users that no longer login via a particular IDP.