W
wood
Guest
Interesting question. Basically, to have some dynamic data/UI shown before the user logs in that has to be exposed at a different endpoint that is public and unauthenticated. This could be raw HTML that you include on the page, or it could be a rest service the returns data that you bind in the mobile app UI. Regardless it needs to be at an unauthenticated endpoint. If it is REST data I assume it is read-only so you could just bind to it as a rest service easily. You could use the JSDO as well (although I am unsure of the specific steps to support what is effectively two OpenEdge Mobile endpoints with different authentication). Note that the marketing endpoint could be any .war file or web app on your Tomcat server but you will have fewer CORS issues if it shares the same port as domain URL (so both should use http or https and the same server DNS and port). =
Continue reading...
Continue reading...