Contents x
    Github - Remove User Extensions
    • 18 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Github - Remove User Extensions

    • Updated on 18 Sep 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Github - Remove User Extension removes a user extension for each GitHub user retrieved from the saved query supplied as a trigger (or users selected in the asset table).

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    Note:

    General Settings

    • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
    • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

    • Use stored credentials from the GitHub adapter - Select this option to use the first connected Github adapter credentials.
      • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • GitHub Domain (default: api.github.com) - Enter the GitHub domain to use when running the Enforcement Action.

    • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

    Additional Fields

    These fields are optional.

    Connection and Credentials

    When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

    • Organization - The GitHub organization name.
    • Authorization Token - The GitHub access token.
    • Authenticate Using GitHub App - When selected, uses the GitHub app to authenticate.
    • GitHub App ID - The GitHub App ID.
    • App Key File (pem) - The GitHub App Key file. Select a file and click Upload File.
    • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
    • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
    • Gateway Name - Select the Gateway through which to connect to perform the action.

    APIs

    Axonius uses the GitHub - Remove a repository from an app installation API.

    For more details about other Enforcement Actions available, see Action Library.

    Was this article helpful?
    What's Next