01:38:17 AM
3EG03IHPV
You're probably right, we may have added some additional, undocumented security checks on version 1.06.
The reason why those changes could have not been documented is that they don't affect "normal" FAS operation and support scope, so it's difficult to explain them clearly and effectively.
I do confirm that, by design, from the very beginning of FoxinCloud Application Server, implementing wuserGet/Set is crucial for secured applications.
Failure to do so results in the inability to access application's forms, which is, IMO, a sound and secure behavior.
I get it better now, but there are two issues I still cannot understand:
1. The problem exists even for public non-secure app.
2. I can compile with 1.05 and I have no problem no matter public or specified users. And I never use wuserget/set. If I compile with 1.06 it does not work public or secure users (not using wuserget).
3. if I understand what you are saying, 1.05 or 1.06 should be no different, and not calling wuserget/set should work with public app just no with secure app, yet both those statements do not seem to accurate.
