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

Authentication error when using OAuth Client #12

Open
stoffelio opened this issue Jul 29, 2020 · 7 comments
Open

Authentication error when using OAuth Client #12

stoffelio opened this issue Jul 29, 2020 · 7 comments

Comments

@stoffelio
Copy link

Not sure GoTo have changed things on their end or the documentation is incorrect.

You talk about creating an App under "My Apps", but this menu option does not exist in the developer back end. Trying to use an OAuth Clients, which is the option I see in the menu, only results in an authentication error.

Slakbal\Gotowebinar\Exception\GotoException : Unauthorized - Could not authenticate with the provided credentials.

@slakbal
Copy link
Owner

slakbal commented Sep 29, 2020

I'll take a look. Goto deployed a new developer backend. Once a client app is setup you're supposed to get the credentials: key and secret

@dankinchen
Copy link

Yes the new location is under OAuth Clients (https://developer.logmeininc.com/clients). BUT this app uses the DIRECT Login. This page specifically says that any NEW OAuth Clients will not be able to use it as it has been deprecated.

https://developer.goto.com/guides/References/05_Direct-Login_migration/

Once you figure out your credentials and authorize your app, you will get "Invalid_client".

@wize-wiz
Copy link

@slakbal I started a PR to get this done. Anything you wish to change/add/remove, be my guest.

Receiving an authorization code needs to be done manually, the API does not offer any other way to automate this process. Although I'm thinking of trying Dusk to see if I'm wrong 😄

@stoffelio
Copy link
Author

@slakbal - have you had a chance to look at the PR? Would be great to get this merged.

@slakbal
Copy link
Owner

slakbal commented Jan 8, 2021

Hi Everyone,

Sorry about the delay, the 2020 dumpster-fire just burned me out a bit. I'll be reviewing everything on the package starting next week. Will keep you posted.

@slakbal
Copy link
Owner

slakbal commented Jan 8, 2021

I just read on the Goto Docs: https://developer.goto.com/guides/References/05_Direct-Login_migration/

**Integrations with System Users** If the username and password that you use in the password grant flow doesn’t represent real end users, the authorization code flow might not be a good fit for your integration. The process for migrating clients like yours will be defined later and you can continue to use the password grant flow until then.

Did anyone find some other information on this yet for system to system integration?

@stoffelio
Copy link
Author

stoffelio commented Jan 28, 2021

Reading the guide: https://developer.goto.com/guides/HowTos/03_HOW_accessToken/
Sounds to me like the authorization code needs to be created manually once, but after that we can talk to the api using an accesss token, which can be requested using the refresh token, with the latter being valid for 30 days.
Am I missing the issue?
Edit: So just create a new OAutch client and use the new way I guess.

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

No branches or pull requests

4 participants