-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using Netlify ID, Can't login #114
Comments
@sogen What is the registration preference set to for your site? Open or Invite Only? You can access it at |
Invite only
… On Oct 10, 2017, at 8:56 AM, Bryce Kahle ***@***.***> wrote:
@sogen What is the registration preference set to for your site? Open or Invite Only? You can access it at https://app.netlify.com/sites/<sitename>/settings/identity.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
So the error message you are receiving is because you are trying to login with Github using an email which has not been invited. |
No, the error was trying to login using *only* the Netlify ID login.
After that, I enabled the Github login, the GitHub login worked fine.
So, to summarize:
The Netlify ID didn't work, that's when I got all the errors about the
password and recovery emails.
…On Tue, Oct 10, 2017 at 11:31 AM, Bryce Kahle ***@***.***> wrote:
So the error message you are receiving is because you are trying to login
with Github using an email which has not been invited.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#114 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACp8Q-fUX7lo_iT9cTaO16TWIz3xG_ZWks5sq6oIgaJpZM4PuYPq>
.
|
I'm confused, logging in using Github is part of your reproduction steps and the issue title. |
Oh, sorry, must have been late, I'm wrong. Note: I signed up to Netlify using Github, and noticed my Netlify account didn't have a password assigned, in case that helps. |
@sogen To clarify, your Netlify account is completely separate from any accounts you setup for a particular site. You will not be able to login using your Netlify account, but must create an account for each site that has identity turned on. |
This is not intuitive. The default behavior should be the site inheriting the site creator's authentication method, including provider. Even if the login and approval has to be done again, a button should exist to facilitate the setup. |
That is a big assumption to make. If you created a Netlify account using Github, that in no way indicates you want your site to accept Github logins. |
Have you tried registration from Identity tab in Netlify admin page? |
I have the same problem too. I can't even login to my Netlify account |
do we need to add in netlify identity page? |
I have this issue as well. Repro Steps: Enabled GitGateway |
while trying to Login with Netlify Identity getting this Failed to load settings from https://github.com/robertcoopercode/gatsby-netlify-cms/.netlify/identity |
I had the same issue, but then I realized it occurs after I made my repo in Github (with netlify CMS hosted in Netlify) private. Changing the github repo back to public should solve the problem. |
This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks! |
This issue was closed because it had no activity for over 1 year. |
i m having the same login issues |
- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
Can't login using netlify ID
- If the current behavior is a bug, please provide the steps to reproduce.
Inside app.netlify, go to Identity tab
Go to /admin to login
Try to log in using Netlify ID
Get error message
Related to #113
Note: I signed up using Github, and noticed my Netlify account didn't have a password assigned.
- What is the expected behavior?
Login with Netlify ID works
- Please mention your Go version, and operating system version.
OSX Sierra
The text was updated successfully, but these errors were encountered: