You’re offline. This is a read only version of the page.
Any user on a AADJ device cannot authenticate to the AOS server.
All other applications and resources authenticate properly on AADJ devices.
Any user on a HAADJ device authenticates properly.
The problem seems to lie in the authentication flow itself, not the device or user.
It might be ties to how AX handles authentication using SID, users on AADJ devices get a sid starting with "S-1-12-1" instead of the AD sid "S-1-5-21".
Changing the SID in the UserInfo table has no effect.
The Enterprise Portal is not an option in our usecase as some modules are not designed for it.
The AX2012 client "supports" windows authentication but seems to handle it in a different way compared to other applications.
Have you heard of this problem and do you know of any workarounds for this problem (other than VDI or RDGateways).
Hi Halldora,
The AX 2012 client authenticates with AD only. You can read about this in the System requirements guide: www.microsoft.com/.../details.aspx
Share
Report
All responses (
Answers (
300,911
