HI Sander, We have zero access to the routers from the outside world. Using http resource, I am actually able to authorise the client successfully - the problem is that the request is cancelled. I know it gets to the router since I'm logged in when I hit that end-point.
For the short-term I've done two things: 1. Return a true from the rejected / canceled request 2. Pre-authorised the users server side The latter implementation means I can be 99% certain the authentication servers will respond with an accept but it's not really that awesome. If we lose the router duing the call, I have no way of checking either. I need to find a way to get the full response from the request. I tried using an interceptor but again, that doesn't do much other than give 0 status. Do you think a lower level library would help? Thanks for your comments and help :) S On Thursday, 22 January 2015 12:21:54 UTC, Sander Elias wrote: > > Hi Simon, > > Yes, that's a bit more, but indeed. That might be a solution. However, you > can let your server do a simple request to the router on behalf of the > client. A full blown proxy might be a bit of overkill. > There is this other point. Can you reach the routers logon from the > internet, or only from withing your client? If the last is the case, a > proxy won't help you. > > Regards > Sander > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
