OpenEdx nutmeg oauth2 - oauth-2.0

I am trying to configure my openedx installation to use third party authentication using google. I got client ID and client secret from google and I followed the instructions here https://discuss.overhang.io/t/social-login-configuration-for-edx-as-plugin-in-tutor/1746 but I still can't see the google button on openedx.
What am I doing wrong?

This is quite a late reply, but I ran into the same problem today. Hope this reaches anyone else with the same problem.
After some hours of debugging and trying out different stuff, I fixed it by using no Icon Class in the Admin panel. I just deleted the fa-google-plus text, uploaded my own logo and that did the trick!
I'm guessing the Edx documentation is outdated and the Google icon is not called fa-google-plus anymore?

Related

Google file picker returning 401 error

Hi I am developing web application and i am trying to implement google file picker api. I have created project in google developer console. I have created API key and OAUTH 2.0 Client ID. I am following http://seanamarasinghe.com/developer/google-picker-with-drive/.
I have attached sample screen shot.
When i upload files i get error The API developer key is invalid. I am running the application in localhost as http://localhost:11726/FilePicker.html.
I have entered http://localhost:11726in origin. Please find below screen shot.
May i get some help to fix this? Thank you in advance.
That's easy. Remove .setDeveloperKey(developerKey) code from your createPicker() function. I don't know why Google is adding this API here exactly, but it is not needed as you already have the OAuthClientID. If you remove that part, your quickstart sample will work.

React-Native: Google Custom scheme URIs are not allowed for 'WEB' client type

I am creating application in React-Native and it has Google Login. I research on it and I got Google-React-Native from here. I added it and follow all the steps which it say. But I am still getting error. I spend two days behind it, but didn't get any solution.
I also follow this-solution, but my issue is still not resolved. Can any one help me to find the solution?
Its a very small mistake. The issue is in generating key for Google. I follow below steps and generate new key and its work for me.
1) Open “https://console.developers.google.com” and generate one application.
2) You will get three menu on Left size. Click on “Credential” tab.
3) You will get new window with three option. “Credentials”, “OAuth consent
screen” and “Domain verification”.
4) Click on Credentials and then "Create Credentials" from it.
5) Click on OAuth Client Id and fill information. You will get the one key.
Use it into your application and it will work fine.
Hope these steps will help to other guys also.
Happy Coding

Firebase 3 Password Recovery Link Not Working

I've been working on my app with Firebase for several months now. I hooked up the password reset code about 5 months ago and when I would test it, I'd get the password rest email sent, click the link and everything would work fine. I haven't signed in with that particular account in 5 months so I forgot the password. Now when I get the pw reset email everytime I click the link I repeatedly get:
Try resetting your password again. Your request to reset your password
has expired or the link has already been used
I'm using Firebase 3 via cocoapods as of Aug 2016 and never upgraded or installed anything from any of the older versions. I'm also using swift 2.2, Xcode 7.3.1.
I would upload code but everything is working fine because the email is getting sent, the problem seems to be on FB's end.
What's the issue?
This is an update for anyone who runs into this problem. This is the response Firebase tech support sent back. It isn't the answer but rather an idea of what they'll ask you if you have the same problem. You get up to 5 free questions per 365 days so why waste one.
Hi there,
Could you please try resetting your password on your console and let
us see if it works there. Also, did you generate a new API key for
your project? If yes, then it's possible that your old API key is
still being used by your app. Could you please check whether the API
key is same? The API key from your Firebase project and your app
should be the same.
Please update your app's Firebase config and check if the API keys
match your console's. For Android, download the updated
google-services.json file. See more details here. For iOS, download
the updated GoogleService-Info.plist file. See more details here. For
Web, follow the config as seen in the docs. If the steps above still
doesn't work, please provide the details below to further investigate
the issue. Old API key and new API key used. Platform and Firebase SDK
version used? Date and time you started encountering this issue. Error
logs and full stack trace. Screenshots of your API keys. Let me know
if you have any other Firebase related issues/questions. Thank you for
using Firebase. :)
I actually had another API key inside my console that was never used. I deleted it like they suggested and the Firebase Recovery email was still broken. I changed my Google.Console password and it still didn't work. I sent them all the required information. As soon as I get a response and hopefully a resolution I'll post it.
I had the same problem. I couldn't understand why and then I realised something... as it was new environment, I exported users from another environment and on this one, I just forgot to activate authentication by email...
My mistake but I thing Firebase should make it clearer in their error warnings.

Unable to be connected to Quickbooks through Intuit App Centre | Playground

Does this link work?
https://appcenter.intuit.com/Playground/OAuth/IA
I am trying to get my QB online token secret required for working with a ruby gem. I have a valid QB account and I have entered my app's consumer key & secret. All I am trying to do is follow the instructions required to get the example app working from
https://github.com/minimul/qbo_api
Every time I click on the Connect to Quickbooks button, I just get an error message.
Oops! An error has occurred.
Please close this window and try again.
Error Code: no_access_to_this_field
Message: Team Intuit IA Application not allowed to get access to QuickBooks
I have changed the urls in my app and I still cannot get past the error message. I am at a loss since this seems to be a very basic step to start working with the gem. Please tell me the newbie mistake I am making.
Is there any other SDK I need to install? I do not have a Desktop version...just the online version.
So if anyone here happens to not figure out this answer already, its because I set the "Access Token Duration:" option on the Intuit Playground to 120 seconds...the default option.
I changed it to 1200 seconds by mistake, and the login works just fine now! I don't understand why that works, so if someone could answer that I could understand it better!
Thanks #William Lorfing
This can happen if you are using the playground to generate Oauth tokens for either QuickBooks or Payments access and you are not setting the correct data source.
See the answer here: https://intuitdeveloper.lc.intuit.com/questions/1247785
regards
Jarred

How to transfer credentials to Glass from Web

Since the "preview" of the GDK is out, I was wondering how we could transfer the credentials of OAuth (say from Twitter) from an AppEngine project (or anything else, open to suggestions) to the APK on Glass. I haven't seen anything on this, and since authentication on Glass would be very hard, how would we do this? I know that I could create a database, but I'm not sure how to make a lightweight version of that. Any other ideas besides a database would be welcome. Thank you for your help.
The easiest way is to have user login on a website, then save OAuth token into a QR code and let the user scan the QR code with Glass.
I have used it in my app Glasquare (Foursquare for Glass), it's all open-sourced:
https://github.com/destil/glasquare
EDIT: There is official way now: https://developers.google.com/glass/develop/gdk/authentication
Maybe you could login from the smartphone version of your app, and transfer those credentials to your glass generating a QR code and reading that QR first time you enter to your Glass app
The video that was published implied there was a authentication step during install but he also said that 'it was still beign worked out'
The bike app (Streva? May have the spelling wrong) does request some kind of authentication
I should add I'm pretty interested in how to deal with oauth in glass also

Resources