We will work on it.
hi @AndrewT
https://github.com/abpframework/abp-samples/tree/master/SignInWithoutSpecifyingTenant
hi uyarbtrlp
Can you share a project or steps to reproduce the issue?
https://support.abp.io/QA/Questions/1020#answer-c2db31bb-d334-9fd6-53e4-39fb98308bce
hi @AndrewT
I will prepare a demo.
https://github.com/abpframework/abp/issues/8281
As I mentioned above, the Identity Server -> Client does not appear when I logged in as tenant admin, so I could not grant permission to this client on the tenant level.
The relevant entities of the identity server are not multi-tenant. You can only grant permissions to client on Host level.
the Authorize does not allow multiple policies, how to combine it with the custom policy for identity server client?
context.Services.AddAuthorization(options =>
{
options.AddPolicy("YourPolicy", policy => policy.AddRequirements(new IAuthorizationRequirement[]
{
new Volo.Abp.Authorization.PermissionRequirement("Abp Permission Name 1"),
new Volo.Abp.Authorization.PermissionRequirement("Abp Permission Name 2")
}));
});
[Authorize("YourPolicy")]
public class TestingTenancyAppService : ApplicationService, ITestingTenancyAppService
https://docs.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-5.0
hi @AndrewT
Use subdomain to confirm current tenant is no problem. https://docs.abp.io/en/abp/latest/Multi-Tenancy#domain-subdomain-tenant-resolver
There is a problem in angular. It fixed in 4.3. https://github.com/abpframework/abp/issues/8231
I will provide angular examples after 4.3, currently there are mvc and mvc tiered examples. https://github.com/maliming/DomainTenantResolver
Yes It will be fixed in 4.3.