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

use guide #81

Closed
SnijkoVladislav opened this issue Feb 28, 2016 · 4 comments
Closed

use guide #81

SnijkoVladislav opened this issue Feb 28, 2016 · 4 comments

Comments

@SnijkoVladislav
Copy link

We have created a config . what's next?
Tell please. that needs to be done in the controller.

@anand9
Copy link

anand9 commented Mar 22, 2016

even i am wondering what to do next

@devane001
Copy link

@ProstoVladislav
OAuth.getAccessToken(user, options); return a response promise and you can execute a callback.

eg:

var promise  = OAuth.getAccessToken(user);
promise.then(function (result) {
    $rootScope.access_token = result.data.access_token;
})

@jmwilkinson
Copy link

The really confusing thing is why you need a username and password to retrieve user data... isn't the whole point of oauth moving the necessity to get a username and password to the auth provider?

The documentation should contain an SSCCE... which it doesn't right now.

@ruipenso
Copy link
Member

ruipenso commented Aug 9, 2016

Basically, after configuration you can use the getAccessToken method on your controller. By sending the username and password, it will store the access_token which will be used in the next request as an Authorization.

@jmwilkinson There are different ways to obtain authorization.

It would be great to have a better documentation and an example, but honestly I don't have time at the moment.

Duplicated by #67.

@ruipenso ruipenso closed this as completed Aug 9, 2016
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

5 participants