# GitHub

### To configure GitHub, enter the list of GitHub Enterprise IDs you want to allow access to.

Access to all other GitHib accounts will be blocked.

<figure><img src="/files/rgXVOOtjrf7450UTwPLN" alt=""><figcaption></figcaption></figure>

### Default Bypass List

There are 3 GitHub domains in the Dope Default Bypass list that need to be set to 'Do Not Bypass', these are \*.github.com , \*.githubcopilot.com and \*.githubusercontent.com.

{% hint style="warning" %}
If these domains are not set to 'Do Not Bypass' this GitHub CAC feature will not work correctly
{% endhint %}

### SSL Cert Errors

Once these domains are set to 'Do Not Bypass' endpoints running the dope agent may see some SSL cert errors for GitHub traffic. To ensure this doesn't happen running the following commands on all endpoints will solve for this issue.

#### Windows

```
git config http.sslcainfo C:\ProgramData\dope.security\res\certs\dope.security.root.crt
```

#### macOS

```
git config http.sslcainfo /Library/Application\ Support/dope.security/res/certs/dope.security.root.crt
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://inflight.dope.security/dope.console/dope.swg-policy/cloud-application-control-cac/github.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.