You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user creates a tenant he needs to go to Log in via SaaS provider to get into his sub domain. I think we can avoid that step, because we know the environment. We can check if the user trying to log in is a share user, so we ask to the provider and then log in.
So, the user could be log in through the portal and the sub domain. I also add a link in the portal where the logged user can go to the sub domain.
The text was updated successfully, but these errors were encountered:
Do I understand correctly, that subdomain database sends login and password to provider and then authorise a user?
I agree, that there one extra step. But if a user has several tenants, then with your solution he has to type password in all tenant. While with a OAuth solution he has to type password only once in a provider website.
Anyway, can it be a separate module or customisable feature? It also applies for any other features. The idea is to create saas kit, so provider can built a system with a features he need.
When a user creates a tenant he needs to go to Log in via SaaS provider to get into his sub domain. I think we can avoid that step, because we know the environment. We can check if the user trying to log in is a share user, so we ask to the provider and then log in.
So, the user could be log in through the portal and the sub domain. I also add a link in the portal where the logged user can go to the sub domain.
The text was updated successfully, but these errors were encountered: