Common problems with GitHub sign-in
| What you see | What to do |
|---|---|
In the Configure GitHub window, under Client ID: Client ID is required | Paste the Client ID of your OAuth app. |
Under Client Secret: Client Secret is required | Paste the client secret of your OAuth app. |
On the sign-in page, Continue with GitHub is disabled, with Sign-in disabled: license is not active | The instance has no active license. In Administration, click Licensing and configure it. |
Someone who signs in with GitHub reads Your account is not known to Astrolabe yet. Ask your administrator to add you, then try again. | The members of your GitHub organization are not in the catalog. An administrator opens Administration › Authentication, clicks Open Catalog › GitHub in the warning, then on the GitHub card Configure, ticks Import GitHub members and teams and clicks Install. See Import the members. Once the import has run, the person tries again. |
In Administration › Authentication, above the cards: Nobody can sign in with GitHub yet: an account must be in the catalog first. | Click Open Catalog › GitHub and import the members, as above. |
Still stuck?
Write to support@forgeit.fr.