Overview#
On EJO Cloud, both the signup form and your organization's sign-in page have Continue with Google and Continue with GitHub buttons. They let you sign in with your Google or GitHub account instead of a password.
Note: Signing in with GitHub is only a sign-in method; it has nothing to do with which SCM your repositories are on. If you use GitLab or Azure DevOps, you do not need a GitHub account; sign in with an e-mail and password or with Google. For connecting repositories, see Connect your source control.
EJO only uses an e-mail address the provider reports as verified:
- On Google, your verified e-mail address.
- On GitHub, your primary, verified e-mail address. GitHub's private
noreplyaddress is refused.
Sign up with Google or GitHub#
- On the signup form at ejocloud.com, press Continue with Google or Continue with GitHub.
- Sign in at the provider and allow access.
- The form comes back with your verified e-mail address filled in. No e-mail or password fields are shown.
- Enter the organization name and subdomain, accept the terms and submit the form.
Since the provider has already verified your e-mail address, no verification mail is sent; your signup goes straight to approval. As the organization owner, you later sign in with the same provider. For the full signup flow, see Quickstart.
Sign in to your organization#
Your organization's sign-in page (for example https://acme.ejocloud.com) shows the same buttons under the password form.
- Signing in never creates an account. You sign in to the existing account whose username is that e-mail address.
- So an admin must first add you on the Users page, with your e-mail address as the username. See Users and roles.
- Your role is the role of that account.
- A disabled account stays disabled.
If there is no matching account, you see: "No account in this organization uses that email address. Ask an admin to add you, then try again."
2FA and SSO#
- Google or GitHub sign-in does not ask for EJO's authenticator code. The provider's own 2-step verification is the second factor, so we recommend turning on 2FA for your Google or GitHub account.
- An organization-wide 2FA requirement does not affect these accounts. See Two-factor authentication.
- An organization that has company SSO set up shows no Google or GitHub buttons on its sign-in page.