virtualGetForm 404 when accessing Aras through Nginx
Hi, I’m running Aras Innovator 14.35.0.44037 behind an Nginx reverse proxy. Setup: Client ↓ HTTPS Nginx ↓ HTTPS :15018 Aras Innovator External URL: https://aras.veconnected.in/VECS_ARAS/ Nginx: location /VECS_ARAS/ { proxy_pass https://127.0.0.1:15018/VECS_ARAS/; proxy_ssl_verify off; proxy_http_version 1.1; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Prefix /VECS_ARAS; proxy_buffering off; proxy_request_buffering off; } Most Aras Client requests work correctly through Nginx and return: status=200 upstream_status=200 However, when opening Item Forms, the following request returns 404: GET /VECS_ARAS/Client/X-salt=3_14.35.0.44037-X/scripts/virtualGetForm? formId=47B8630E2B4C40C1B23C6EE9962F7681& formLastModifiedDate=2025-05-29T19:48:04.24& languageCode=en& itemTypeId=450906E86E304F55A34B3C0D65C097EA& itemTypeLastModifiedDate=2025-05-29T19:44:47.74& databasehash=3a52875cf3d26f02& mode=add Chrome reports: 404 (Not Found) In some cases DevTools reports: 404 (Not Found) (from service worker) Important observations: The same form works when accessed directly from a browser on the Aras VM. Other X-salt resources work correctly through Nginx. Metadata requests and InnovatorServer.aspx requests return 200. I cannot find the virtualGetForm request in the Nginx access log when the client gets the 404. Aras service-worker.js is registered and being served. The problem occurs with multiple forms. Could virtualGetForm be intercepted by the Aras service worker/cache and returning a cached 404? Is there a recommended way in Aras 14.35 to invalidate/reset the client service-worker/cache, or any known Nginx configuration requirements specifically for virtualGetForm?
[ARAS 14] Change display order of authentication options
Hello! My company is using ARAS Innovator 14 (release 39). We have two authentication options: Entra ID SSO and local user. By default, the local login option is displayed first in the login page, and we have to choose the SSO option from the drop-down menu. I want to know if there's a build-in method allowing me to change the display order of those two authentication options? Like a config file, a button on AWS console, etc.? I have read through the ARAS documents come with the installer, but there's nothing regarding this matter. Searching through Google and AI didn't help me find any discussions about this topic too. If anyone know about this, please share your experience with me! Thank you! Here's the screenshot of the login page. The 'Aras Innovator' option allows me to login using local username and password. The 'Azure AD' allows me to login using my company SSO account. Extra discussions: My manager also asked if we could disable the local login option, only leave the SSO one in the login page. As I understand, this is not possible with the backend of ARAS, as each SSO user need to be associated with a local user of the same name. And we should keep the ability to login ARAS with local admin/root account in case SSO has issue. But that's just my understanding, please correct me if you have different opinion/best practice about that!
