Resolution
Problem was escalated to escalation engineers where we confirmed the behavior of the application.
In AX 4.0 for the LoginProperty class, we had two properties on this class – setUsername & setPassword – these were the properties you used if you wanted to change the login, see link below…
http://msdn.microsoft.com/en-us/libr...(v=ax.10).aspx
In AX 2009 onwards, these were removed for security reasons – see link below, they setUsername and setPassword are no longer valid properties.
http://msdn.microsoft.com/en-us/libr...(v=ax.50).aspx
I have looked at the kernel code, and in AX 4.0 and before if you specified the setUsername and setPassword then the kernel would use these to create the ODBC connection. If they were not specified, then they would use the login for the AX AOS service (or with AX 3.0 or before the client login in two tier mode).
So as it is no longer possible to set these properties
from AX 2009 onwards, the kernel will always use the login for the AOS service. So even if you try and set these in the “setOther” property on the LoginProperty class, they are ignored as in the connection string we create in the kernel code is always using trusted authentication of the AOS Service account – so these additional properties are ignored.