Flat File Import Process
Flat File Import Process

Flat File Import Process

The following ladder diagrams show the sequence of events for Importing users into the environment and the elements involved with the device sign-on.
Importing User Logical Sequence
Device Connection Logical Sequence
Profile Client JSON configuration file which is mentioned in the flow diagram is shown below. The Proxy URL and the Proxy API Key are two new elements described later in this document.
All the devices across the Enterprise deployment can use one configuration file when the PFM Proxy service is used.
{ "customer_id": "20", "sfs_url": "https://<pfm-server1>", "proxy_url": "https://<pfm-proxy-server>", "proxy_url_api_key": "<api_key>", "site_id": 199, "log_level": "debug", "confirm_role": false, "power_connected_logout": false, "log_file": true, "config_settings": 0 }
The Launcher issues a broadcast intent to initiate the login process of the Profile Client which is included in the JWT Access Token intent.  For more information about Intent details, refer to the Profile Client Configuration and Programmer Guide.