-
Notifications
You must be signed in to change notification settings - Fork 156
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
.success removed in Angular 1.6 - breaks oauth-ng #149
Comments
Alfsig fixed this in the PR #145 , but it seems that nobody cares. |
I care! Sorry I didn't see this. |
how i can update this fixed??? |
Was this ever fixed? |
Luwangel says yes. It's been a while. I ended up going a different path with oauth. |
@jwmapana -- what path did you end up taking? I am trying to get oauth working with an angularjs client, I tried using this library but there seems to be too many issues with the latest version of angularjs. |
I found a nice workable answer here: https://stackoverflow.com/questions/18218293/angularjs-oauth/23490076 It's the solution that starts with "Here is a simple example using just redirects with angular js". My login page has a controller with the login button tied to this function: $scope.login_oauth2 = function() {
==================== app.controller('accessToken', function ($location,$rootScope,globalFactory) { hash = $location.path().substr(1); splitted = hash.split('&'); for (var i = 0; i < splitted.length; i++) { $location.path("/login"); //this can go to any route you want of course });and then put in a route like this, so when the site returns from google with a token, it processes it in the accessToken route: What happens is, your login view and controller sends the user to google oauth, they authenticate, and google oauth returns to your site with the access token, so your router takes you to this controller, which parses out the results. You can do pretty much whatever you want with it from there. I hope that helps. |
You get this error:
$http.get(...).success is not a function
The text was updated successfully, but these errors were encountered: