Getting a 406 when trying to hit an OData endpoint. Only thing that I can think of would be the authentication method that it is configured for is not supported by the database, which is a copy of production. Prod uses Windows auth against our AD while the development environment that was set up used NavUserPassword. I’m curious if the 406 is directly related to that, and if it is possible to use Windows authentication, as that’s what production uses, and still offer the OData and SOAP endpoints for a needed integration with a middleware connector.