Question: How can errors be surfaced when using Classic Universal Login?
Answer:
When it comes to working with Classic Universal Login we show errors in separate sections. For example:
• An invalid password error for a database connection is shown on the Universal login page itself.
• Certain invalid requests or invalid browser states can lead to an error page being shown
• Whereas other conditions like a blocked user result in an error response being delivered to the client application
Note: flashmessage
can be leveraged when you have Lock implemented to quickly show general type( success
, error
) messages, but its use within Universal Login may not be possible depending on the exact error scenario.
Supporting Documentation: