Hi Liglio, 3) The Mapguide configuration I was referring to was the layers, maps, and all the other things you can see and edit with Maestro/studio, as well as user data. This data, typically XML, can be read and written via REST calls. An example of these rest calls can be accessed via the web tier test page (http://localhost/mapguide/mapagent/ ). There are also call you can make to retrieve and create users and roles. By doing this step, I can guarantee that each Mapguide server has the same layers, data, maps, users, etc. Typically I do not touch the serverconfig.ini files.
6) Rather than creating a Mapguide account for each user, I hand over authentication to the company’s identity management service, typically Azure AD. To do this, you have to first register your Mapguide site as an app within Azure (here is a video on how to do that https://youtu.be/YWvl0cIilyA). Once the app is registered, the user’s login process looks something like this: a) The user goes to the load balancer address (which I will call the Mapguide site from now on) in a browser. b) If the user doesn’t have an auth token, they are redirected to the company’s azure site to login, using their corporate account. c) After successful login, they are redirected back to the Mapguide site. d) Once the user has an auth token, I query active directory to see which group(s) the user is in. e) Based on the user’s group information, I will create a new Mapguide session with the relevant Mapguide access. Typically by using generic Mapguide accounts. User sessions are not shared between servers. The sessions are deleted when the user closes their browser, or the server disconnects the user (typically due to timeout settings). Do you have a use case/user story to keep or share the user session beyond its life? Mark
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
