Is it possible to have single table for abpusers and they can be part of multiple tenants where there profile will remain same and few user documents.
abpusers table will exist only in the main db user can login with subdomain of tenant, where it can shared or it's own tenant's personal db in the same server linked accounts switch the user to the other tenants (At the moment with subdomain tenants it is not working, but non-sub-domain tenants it is working)
Is it achievable in abpframework, I know I have to write custom, but where to change the code or start, it will be helpful if you can suggest?
Navigation Property: Current Behaviour: Only string properties are allowed!, UI pick type: 3 options New Behaviour: for non-string properties can we have 4th option for UI pick type: None and display property hidden.
I am not sure if it will be useful for general purpose or not.
Yes
abp install-libs thats it
The pointers you did, I knew about that.
I just now verified the node_modules installation of @abp/zxcvbn and I did abp install-libs just before ending the day yesterday. You are absolutely correct it was just package update issue when I migrated from 7.4.4 to 8.0.2, so there is no relationg with the fixes I did and I reverted to old code phew!
By adding @abp/zxcvbn it made no difference as it was part of "@volo/account": "~8.0.2".
Volo.Abp.Account.Pro.Public.Web package was transitive package of Volo.Abp.Account.Pro.Public.Web.OpenIddict that is pre-installed in the AuthServer. I was able to fix it by installing Volo.Abp.Account.Pro.Public.Web in the AuthServer and adding its module in depends on typeof(AbpAccountPublicWebModule). in the AuthServer.
I am not confident the solution I did is correct or not?
Please note, it use to work with abp framework version: 7.. versions
Temporary Workaround:
Configure<AbpBundlingOptions>(options =>
{
options.Mode = BundlingMode.None;
});
Thank you for refund and closing the ticket.
I am having issue from version 7.0 to 7.4 major version, currently it is the same in 7.4.4
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please first use the search on the homepage. Provide us with the following info:
Example:
For Host Domain
Authserver: accounts.test.com Web Server: test.com Api Server: api.test.com
When unauthorized user is making a webcall it calls api.test.com
For Tenant Domain
Authserver: subdomain.accounts.test.com Web Server: subdomain.test.com Tenant Api Server: subdomain.api.test.com
Issue: When unauthorized user is making a webcall from subdomain like subdomain.test.com it calls api.test.com Expected: When unauthorized user is making a webcall from subdomain like subdomain.test.com it should call subdomain.api.test.com
In angular it should not be an issue as it is specificing in the config file {0}.api.test.com
But in MVC it is not working
"RemoteServices": { "Default": { "BaseUrl": "https://{{tenantName}}.api.test.com/" (with or without tenantName interpolation it is not working) } }
I have verified below configuration are correct:
Also, please note api.test.com it works as it is host (Correct Behaviour) subdomain.api.test.com it works as it was created as tenant (Correct Behaviour) wrong.api.test.com it does not work as it was never created as tenant (Correct Behaviour as tenant does not exist with name "wrong")
Please help with temporary workaround or is it a bug?