When the EAM web service is configured to authenticate the user through the OIDC Authentication Flow, the user can log in to the Mobile Offline app with User ID and Password configured with IDP outside of the EAM Server.
The LGNMOB install parameter is not used.
See the HxGN EAM OpenID Connect technical brief for more information about Setup OIDC Authentication flow for EAM server.
For the AD FS environment: AD FS support is from ADFS 4.0 and newer. The OIDC Client must be configured as “Native Application”. See the HxGN EAM OpenID Connect technical brief for more information.
For the OKTA environment: The Client Authentication in the OIDC Client must be set to None. See the HxGN EAM SSO Configuration technical brief for more information.
Additional EAM Mobile Offline setup specific to the OIDC client is required. Users are required to scan an OIDC QR Code for the App to login. Users log in through an embedded browser using OAuth authentication flow. See the HxGN EAM Mobile Offline OIDC Configuration functional brief for more information.
The OIDC Authorization Code Flow is only supported for EAM Mobile Offline apps. OIDC Authorization Code Flow is not supported for EAM Connected, EAM Disconnected, EAM Rapid Request, EAM Asset Move, and EAM Phone Apps.