I thought I’d chime in and express my disappointment in Auth0 here. You’re forcing users into the unknown (into the void) telling them “Just go for it” and when the few survivors come back injured you tell them “Well, whatever, didn’t you purchase our hazard suits? We’re not sure if they’re needed but you can try them as well”. That’s very unprofessional and clearly your team can’t handle it. You still have failed to admit in this thread that Lock doesn’t work without the paid “custom domains” feature (and is useless) and that your documenation is wrong deceiving people and luring them into a trap. Your level of user support is mediocre without anyone caring about this issue which is long-standing and resulting in direct income loss (mac-powered customers) for everyone except you.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Safari. Unable to configure verification page | 1 | 3407 | December 29, 2021 | |
Auth0Lock 11 still show "unable to configure verification page" after setting the Custom Domain | 4 | 4564 | November 10, 2021 | |
Safari - Unable to configure verification page | 4 | 9979 | December 4, 2018 | |
There was a problem with your login: Unable to configure verification page. [error code: server_error] - WordPress | 1 | 4078 | May 25, 2021 | |
Unable to configure verification page in firefox while I am getting access token in chrome | 2 | 1731 | March 29, 2023 |