Tima version:
LHS version:
DeltaTima version:
GeometryServer version:
FMS type:
Client:
Diagnosis and Solution: This occurs for two recorded reasons:
-Because the corporate email that was assigned is not yet included in the client's AD as such. As a solution, the client must be contacted to request that the user be included.
-In the Jarvis-server.nomad In the parameter called OAUTH_ALLOWED_EMAIL_DOMAINS the corporate email domain that we want to use is not registered. As a solution, you must edit and add the domain in the previously indicated parameter and plant the task and start the Jarvis-server again