Hi M-Files fellows
I am facing a problem with the REST API call on a specific environment with a proxy server. So we have a public domain with an ssl certificate, using port 443 and a separate internal m-files app server.
M-Files Web and RPC over http works fine, so the login is possible with the web browser as well as with the desktop client. However, using the REST API call it doesn't work.
I use a module on make.com, which works perfectly with other environments, but on this one I get a time out and checking the windows logs on the proxy server I find this error message:
M-Files: 23.10.13060.5
Due to a user or client operation, an error response with the following reference ID was sent to the client:
9b1f3b0a-fdb0-4e29-8662-ba2cc5de3894
If the error requires further investigation, see below for detailed error information.
Exception Information
Name:
Message: Login to vault failed
URL: /objects
Method: GET
Status Code: 403
Stack Trace
bei MFWS.RestFilters.SecurityFilter.TryFilter(RestMethodInfo methodInfo, HttpContext httpContext, LogicContext logicContext)
bei MFWS.RestFilters.SecurityFilter.Filter(RestMethodInfo methodInfo, HttpContext httpContext, LogicContext logicContext, Stream& inputStream)
bei MFWS.HttpHandlers.RestHandlerDelegate.GetObject(HttpContext context)
bei MFWS.HttpHandlers.HttpHandler.ProcessRequest(HttpContext context)
Browser Information
Browser Name: Unknown
Major Version: 0
Supports Frames: False
Supports Tables: False
Supports Cookies: True
Supports Javascript: 0.0
Supports Java Applets: False
System Information
Operating System Platform: Unknown
- ports should be open
- basic auth is applied (authentication token)
- using postman I can get an authentication token, but also not sending any other call
Does anyone know or assume what could be potential errors according to this message?
Kind regards,
Dario
