If I move the service onto a different box and update my hosts file to point to the new box then WebAuthenticationBroker has no problem reaching it. Seems like WebAuthenticationBroker will just ignore your local machine regardless of what you do.
So it would appear that there are only two options 1) develop your service on a different box, or 2) setup a proxy server to bounce the http request back into the box as suggested on this thread http://ift.tt/MZVe3e
This is a bit of pain for dev, so hopefully there are just some other options I am not aware of.
No comments:
Post a Comment