1. What is the problem? Be very detailed.
Actually I don't have a problem, it is to anticipate.
I have custom php scripts which communicate with ODK Collect.
In ODK Collect v1.30.1, in the configuration screen of the server, i can read this information message
"Custom server paths
Will be removed in a future release. Please use / formList and / submission on your server."
I try odk central in local,
and when i configure ODK Collect with a QR Code generate by ODK Centrale for a form campagne, i see complicate authentification access in ODK Collect side like
URL server : https://mydomain/v1/key/I$O66........o$X/projects/34
without any user and password needed
Does the old authentification by user/password will disappear in the futur of ODK Collect ?
Will the compatibility of the exchange flow between ODK Collect and the old ODK Aggregate project will be impossible in a near future ? (this question because finally my scripts are modeled on this process.)
2. What app or server are you using and on what device and operating system? Include version numbers.
ODK Collect v1.30.1
php script server side
3. What you have you tried to fix the problem?
4. What steps can we take to reproduce the problem?
5. Anything else we should know or have? If you have a test form or screenshots or logs, attach below.
For now the communication was very stable since I used it (2017), i have made any change.
I hope for me that future versions of ODK Collect will be still compatibles with ODK Aggregate flow, like my scripts are based on them.
It is for anticipate problem on my work.