non-interactive (bot) Login fails, possibly because of CORS (AngularJS)

[mascip]

[Solved]: see the 3rd message.

Hi, I'm using AngularJS and Restangular to try and login to the new API. My aim is to make a bot which displays what it does in the browser.

I think I'm encountering a CORS (Cross Origin Resource Sharing) problem. I describe it in more details here.

Could it be that I am not supposed to use the non-interactive (bot) login from within a browser? If that is the case, then could I use the non-interactive (bot) login from curl, and then use my session token to make requests from the browser?

An alternative could be to use the interactive login for this purpose. Or to display what the bot does with another type of graphical interface.

Thank you for any help. I will try the curl-login solution on Monday, but would appreciate any insight.

[mascip]

I just re-read the Documentation, which says

Non-Interactive login - if you are building an application which will run autonomously, there is a seperate login flow to follow to ensure your account remains secure.

The word "separate" might be indicating that it cannot happen in the browser?

[mascip]

Logging in as a bot through the browser was probably not a good idea.

Now I'm building my bot as a webservice (to myself). I can then either push information to my front end with websockets, or query information, from the front end, with REST requests.