Code Monkey home page Code Monkey logo

Comments (8)

andygeers avatar andygeers commented on May 22, 2024

(If I modify the library to use the id_token as though it were a refresh_token, it actually works just fine and fetches the user info quite happily - I just would prefer not to have to modify the library to get it working)

from appauth-android.

iainmcgin avatar iainmcgin commented on May 22, 2024

Client secrets are not required for Google auth, and are strongly discouraged for mobile apps where the secret can be easily extracted from an APK. The demo app that is included in this repository includes instructions for configuring Google authentication, see here.

If you send the right authorization request you should be able to get an authorization code for a refresh token quite easily - the demo app does this already, and uses the retrieved access code for requests to the UserInfo endpoint: see here.

from appauth-android.

andygeers avatar andygeers commented on May 22, 2024

Thanks very much for the clarification. I think I would change the Google integration instructions to clarify that appauth.keystore is created by AppAuth-Android during the build process - I was looking for it whilst integrating the library and of course couldn't find it because it hadn't been run yet. I had assumed it was something generic to any Android project.

from appauth-android.

iainmcgin avatar iainmcgin commented on May 22, 2024

Ah, apologies for that. I tried to simplify the setup process by generating the keystore during the build but as you say this isn't specifically mentioned anywhere in the instructions. I'll try to clarify this point.

from appauth-android.

andygeers avatar andygeers commented on May 22, 2024

On that note: are we meant to copy and paste the generateKeystore task into our own project or is it meant to run automatically when our project expresses a dependency on the library?

from appauth-android.

iainmcgin avatar iainmcgin commented on May 22, 2024

It's just for convenience when developing AppAuth-Android - your own app should have its own keystore for debug and release. You're of course welcome to re-use this if you find it useful, but most apps will use the standard ~/.android/debug.keystore for debug and another more carefully managed keystore for release.

from appauth-android.

andygeers avatar andygeers commented on May 22, 2024

Wonderful, that makes a lot more sense now - perhaps the documentation could explain that (especially that debug path - I was conscious of my production keystore but not the debug one). Thank you!

from appauth-android.

andygeers avatar andygeers commented on May 22, 2024

And now I see that Google documents that location within the tool where you create API credentials... not sure how I missed that last time. Thanks again.

from appauth-android.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.