-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Google Provider OAuth settings for development #2892
Comments
Just did it, i believe! |
Can u check and close this if it works? Thanks @SidharthBansal !!! |
Sorry, it is not working |
Is it working in your browser @jywarren for both ports |
I think it's the domain verification -- but we can't verify localhost...
maybe look around for how this ought to work? Were you able to add these
for your own API account?
…On Thu, Jun 21, 2018 at 6:59 PM Sidharth Bansal ***@***.***> wrote:
Is it working in your browser @jywarren <https://github.com/jywarren> for
both ports 3000 and 3001
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2892 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ-yHsCehzvY-MF5_cL7s0zzaNxg-ks5t_CUegaJpZM4Uy3NP>
.
|
I don't require any |
Is it working on your localhost? |
wait, change it where? are there "trial" ids available for working in
development? Like how there's a "testing" key for ReCaptcha for working
with localhost?
…On Thu, Jun 21, 2018 at 7:23 PM Sidharth Bansal ***@***.***> wrote:
Is it working on your localhost?
Can we change this app_id and app_secret to my app_id and app_secret to
check it in development first?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2892 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJz-ZMjJTReOGK3kcro8hozh8QdH0ks5t_CrLgaJpZM4Uy3NP>
.
|
Yeah I saw that there is testing key for ReCaptcha working with localhost |
No there are not. If we will not be able to configure it ,that will mean that we can't have same id for all developers if we both will be able to log in via google provider that means, we need to change the app_id and app_secret in the jenkins back to the app_id and app_secret which you have created for production and need to modify the app settings OR may be we need to create one more app for developers access. Possible reason for this could be |
I have sent you app_id and app_Secret on jeff@publiclab.org. |
sorry it is late here (much later there! Be sure not to forget to sleep!)
and i have to stop working... but can you explain tomorrow the reason
Jenkins should be changed in relation to localhost? Isn't one up on
unstable.publiclab.org (jenkins) and the other on your computer?
Maybe my brain needs a break!
…On Thu, Jun 21, 2018 at 7:37 PM Sidharth Bansal ***@***.***> wrote:
I have sent you app_id and app_Secret on ***@***.***
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2892 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ33NGdwsJxFxoR9K0dH06LBGcxi9ks5t_C4DgaJpZM4Uy3NP>
.
|
Ok. You take rest. We can continue it later.
Yeah sure. Thanks |
A few things But in the development, we don't have it Also, see
This line says if the environment is production which localhost:3000 is not. So this file doesn't have any role in development. As you mentioned this in #2855 (comment). So, I inspected it by deleting the ENV[''...''].... line. Even then I could not see any change on localhost:3000/signup. This shows that ReCaptcha is not surely available in the development. I don't think we have any other page using ReCaptcha. |
@jywarren Also the form which is rendered inside the signup form says that ReCaptcha is not used in development plots2/app/views/users/_form.html.erb Lines 60 to 88 in 608ee10
|
Well, I guess I'm not sure what we can do here. The settings are created but localhost is not working - possibly due to domain verification which we cannot do for As to the environment variables, you can insert them at run time locally by doing:
Or, you can put it in a file like
and do:
|
If not can you please check it with the app_id and app_secret which I have sent you on jeff@publiclab.org I think this can help to troubleshoot a little bit |
Localhost does not require any domain verification but the websites does. So, in the app_id and app_secret which I have sent you. I have not done any domain verification. |
It's a bit late here, but I will try tomorrow, thanks!
…On Tue, Jun 26, 2018 at 7:09 PM Sidharth Bansal ***@***.***> wrote:
The settings are created but localhost is not working - possibly due to
domain verification which we cannot do for localhost
Localhost does not require any domain verification but the websites does.
So, in the app_id and app_secret which I have sent you. I have not done any
domain verification.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2892 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ0TL6eFp4aDd6FKaLLJkhkyoUtoRks5uAr8bgaJpZM4Uy3NP>
.
|
We have completed Google OAuth provider settings on
The following are left so that the developers can use it in development
We are moving from the conversation of Google Authentication #2771 to here.
@jywarren Can you please make the changes to the Google developers app as you indicated in Documentation added for OAuth #2855 (comment)?
The text was updated successfully, but these errors were encountered: