Safari Browsers on macOS or iOS (Not allowing user to Login)
Hi Support,
I think Caspio should give a notive on this issue. Safari Browsers on macOS & iOS will not be able to login if there is Caspio's Login script on the html which the user can login easily using Chrome, Firefox, Opera and Internet Explorer.
The only fix which is available in macOS & iOS platform is set the Safari's Preferences > Privacy > Disable "Prevent Cross Site Tracking"
And this is great inconvenience to redirect user to disable this setting in their Safari Browsers. Whats more problematic here is ? Even firefox will disable the site tracking in their future development versions soon
which will make this more difficult for the user on the every browser to redirect everyone to disable. And what if every browser jumps into the same boat to disable this setting by default.
So i need you to look into this issue and work on why enabling the prevent cross site tracking is blocking the Caspio's login datapage which is having authentication.
Thankyou.
Vaibhav Arora
shared this idea
Thank you for your feedback. In the upcoming release, you will be able to log in to Caspio applications using browsers with cross-site tracking prevention enabled. This will work for applications deployed with all methods except iFrame deployment. Stay tuned for iFrame solution update in the future releases.
4 comments
-
Robert
commented
It is 2021, and yet no solution to this very important problem. If users can't log in using one of the worlds most important company ( Apple ), what is the purpose of using Caspio services ? Brings no value using this company services. FIX THE PROBLEM ALREADY !!!! WHAT ARE YOU WAITING FOR ? SHAME ON YOU CASPIO !!!!!
-
Justin
commented
When can we expect a fix for this? It has been over a year...?
-
Anonymous
commented
Admin, no your latest release has still not fixed this issue, with or without iFrame deployment. Can we get a current update on the status of this fix?
-
Anonymous
commented
The upcoming release did not fix the log in issue regarding Safari. When can we expect this fix?