Unified identity platform has reduced dev time and secures multi-tenant cloud microservicesI noticed some enhancement challenges. Sometimes when I logged in, there was a thirty-day time period to log in again, but recently after restarting my system, that thirty-day period is not working. I need to provide the token after login again, which is for the security part. For development accounts used by others, every time we need to use those tokens to connect to that site. UI improvements can also be made, particularly on the homepage, where tiles could be displayed. It would help if there were separate left bar tiles for the login section so anyone could edit their login page directly. Everything is working very well. However, when integrating, I need to give permissions and manage many things manually when creating users with multi-tenancy. For instance, I first create the connection, then the organization, enable the connection at the application level, allow some permissions, and create the default user. Improvements could be made so that when someone creates an organization, a default user is available from Auth0 Platform to log in, and they could use those credentials to create further users. This is also dependent on functionality and user requirements. For my use case, that was lacking. The initial setup was somewhat complex. Since I was doing it for the first time, I needed to create an application, allow permissions, integrate it, and set redirect variables and URLs for logout. Although documentation is available, it does not specify the exact format for multiple logout URLs or multi-tenant URLs. Sometimes I had to try different methods until it worked. Improvements in documentation are needed for first-time setups. When connecting with Auth0 Platform, if there is a failure or error, I do not receive a specific message to identify if it is a bug or another type of issue. I suggest having clearer error messages, such as indicating what is missing or providing expected formatting for values.
