I’m just starting trying to use universal login. Go dashboard, enable customisation, the preview has an error:
“Something went wrong. Please contact technical support.”
I guess I can just not use the preview, so I go to the default url that the dashboard states it serves on, this errors too so I check the logs and get: “missing client parameter”.
What do you want from me? Its really unclear. I guess I need to add a parameter to the query string?
A message from an auth0 employee in this forum states:
As mentioned, You should never visit /login directly
Then don’t link it or make it this clear when the url is exposed on the dashboard (link to /authorize instead?). I’ve read that post and I still don’t know what I need to do to literally just make sure the sign in form is displaying the correct logo.
Sorry if I sound a bit frustrated but its disappointing the amount of extra domain burden I need to chomp through to complete what should be a simple task.
k, I’m now hitting the /authorize end point (I finally chewed through all the links in that post to find what I wanted) and that gives awesome errors enabling me to error my way to where I need to be. So now I’m merrily customising things but I still wanted to point out that it requires some belligerence to get here.
I would also suggest that it would be value to link to this: https://github.com/auth0/lock#customization from that customisation page somewhere as it contains all the docs for basic customisation of lock which is likely gonna be a big chunk of the use-cases.
Also can I just say I enjoy working on this stack in general. The docs are very detailed and mostly do a great job and that the clients are all open-source is soooo useful for developer volition. If you know of the person/persons who decided on open sourcing them give them a high-five from me.