Skip to content
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

Twitter Provider App Settings #2893

Closed
4 tasks done
SidharthBansal opened this issue Jun 22, 2018 · 17 comments
Closed
4 tasks done

Twitter Provider App Settings #2893

SidharthBansal opened this issue Jun 22, 2018 · 17 comments

Comments

@SidharthBansal
Copy link
Member

SidharthBansal commented Jun 22, 2018

This is for future reference for Twitter Provider in OAuth Login Project.
This is part of checklist #2676 's Twitter Provider.
A few points:

  • Twitter app is not functional in the insecure version of development mode. That is, Twitter works only on https(http+ssl by openssl gem) in development. We use port no 3001 for https connection
  • We can't use https://localhost:3001 in case of Twitter. Instead, we need to use https://127.0.0.1:3001
  • We need to give privacy url for development mode in addition to production. Make the privacy url as needed @jywarren
  • We need to give Terms of service for development mode in addition to production. Make it as needed @jywarren
  • We need to enable email address otherwise email is not accessible by going to advance settings
  • We need to add sign-in capability
  • There is only one origin url, hence there is a need to create different apps for the following:
  • https://unstable.publiclab.org
  • https://stable.publiclab.org
  • https://publiclab.org
  • https://127.0.0.1:3001
    These are the screenshots of the settings made which are functional dated 22.6.18
    image
    image
    image
@SidharthBansal
Copy link
Member Author

Please don't get dishearted if you log in via twitter from https://127.0.0.1:3001/auth/twitter and you see you are not logged in at public labs. Check the url. It will be https://localhost:3001/
You are actually logged in on https://127.0.0.1:3001 but not on https://localhost:3001.
So check it on https://127.0.0.1:3001

@jywarren
Copy link
Member

OK, is this ready to go now and I should set up the app? Thanks!!

@SidharthBansal
Copy link
Member Author

I have sent the patches in #2948 and #2947 which are required before the twitter app setup. After merging them you can set up the app in your free time.

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Jun 29, 2018

Once you will make the app_id and app_secret and place it in jenkins. Please ping me. I will start writing the tests for Twitter.

@jywarren
Copy link
Member

OK - those are both merged, great!

@SidharthBansal
Copy link
Member Author

Now you can set up the twitter apps.

@SidharthBansal
Copy link
Member Author

Thanks for the merge

@jywarren
Copy link
Member

Do you need just the Consumer API Key and Secret, or also an access token and secret?

I've added the Consumer Key and Secret to unstable, staging, and production!

@jywarren
Copy link
Member

I set it to read only for now. Want to test this out on unstable?

@SidharthBansal
Copy link
Member Author

Do you need just the Consumer API Key and Secret, or also an access token and secret?

Only Consumer Key (API Key) and Consumer Secret (API Secret) are needed.

@SidharthBansal
Copy link
Member Author

I have pushed the changed to unstable.

@SidharthBansal
Copy link
Member Author

image
Working fine

@SidharthBansal
Copy link
Member Author

@jywarren can you please push the changes to the production and stable.publiclab.org.
Thanks for setting up the apps.

@SidharthBansal
Copy link
Member Author

@jywarren stable is working fine. Can you please push the changes to the publiclab.org and if publiclab.org/auth/twitter works close this issue?
Thanks

@jywarren
Copy link
Member

jywarren commented Jul 2, 2018

OK, we'll schedule this probably for tomorrow!

@SidharthBansal
Copy link
Member Author

Great.

@SidharthBansal
Copy link
Member Author

Working fine in production.
Thanks @jywarren

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants