From what it sounds like, they don’t provide a way for a user to stay logged in. It just gets stored in the header and cached when you access via a web browser. I’m not sure there is anything we can put into a swagger file to make this function like they expect it to function if it were initiated from a browser. They keep users logged in within their own applications so I have inquired with them on how they implement this. Hopefully they can share some insight.
I’m going to add a little backstory here on what we are trying to accomplish in case this helps anyone in the Dropsource community. This is app that I am building is for a restaurant group that has a loyalty program for beer. The point of sale software captures the customer information and then we have access to their API to use that data how we please. Ultimately, all we really need from this API is the customers loyalty points balance, their list of beers they have purchased and then any balances if they have any money on their account to use in our stores. After doing some fairly heavy testing of multiple scenarios, I have come to the idea that I will probably need to utilize 2 API’s for this project. I believe that Backendless provides the necessary components to handle a more robust customization of our customers profiles and how we can communicate with them via push messages and emails. We can also control their sessions while using the app and handle the experience a little bit better. It’s a bit of a challenge but I think I have found a way to register a customer in both Backendless and our other API at the same time. Since the customers loyalty account is tied to a specific loyalty card number, we can actually our POS’ API with the card number, store that in our Backenedless customer data and then access this loyalty data at any moment without actually having to login to the POS API. That gives us a ton of flexibility and allows to take advantage of Backendless’ many offerings.
Our POS provider is hopefully going to respond today with how they handle customer logins. Their web applications are written in Java and I have my fingers crossed that they will shed some light on what their process is. My assumption is that they using a mix of both browser caching and some server side scripting to accomplish this. I can see that a java session token is created when I login to any of their sites and then that is cached in the browser.
Sorry for the long winded post. Hopefully that provides some insight on what we are accomplishing and maybe it will help someone else to accomplish their development goals as well.