Activities of "roberto.fiocchi"

• ABP Framework version: v8.1.0-rc.3
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Description The popup shown with the validations of the form that contains more than one error is displayed in a single line instead of multiple lines.

Reproduction Steps Create a form with inputs and make validations on it

Expected behavior The details of the validation should be multiline

Actual behavior It's displaying in a single line even if it has more than 1 validation

The request is similar to this Issue (but I use blazor WASM instead of MVC): https://github.com/abpframework/abp/issues/19274

But since you use Blazorise, can you also integrate the BlazeSpark - Admin & Dashboard theme from Blazorise?

Our customers ask for a similar layout. Which is very similar to that of AspNetZero.

And the chat module should open in a disappearing overlay or in a popup and not on the page, so the users don't loose the work that they are you doing.

We would also need a notification module as was present in AspNetZero, when is its development planned? See https://docs.abp.io/en/commercial/latest/aspnet-zero-vs-abp-commercial -> Real Time Notification

Thanks, Roberto

Ah ok, so only Lepton has the Application theme so I have some questions about it. Does Abp Commercial support Lepton or is it deprecated? Abp Commercial plan to add new layouts like https://startbootstrap.com/theme/sb-admin-2? Is it possible to have a quote to have a layout of that type plus the management of realtime notifications and chat like in AspNetZero?

Thanks

Ok, I will also try this solution and I will give you feedback.

Thank you!

Hi,

What method do you recommend doing this?

In fact the implemented workflow is that the admin registers a user with name.surname@mydomain.com and only then can he access the web portal. This seems to me to be the only solution to block access to unauthorized domain users. Or are there other options?

Thanks

Hi,

I tried the code you suggested but it seems like it automatically registers the user which is not the behavior that i needed. I needed to block the user from self-registering no matter the origin (local or external provider). Digging through the code i might have found a solution:

public override async Task<IActionResult> OnGetAsync()
{
    ExternalProviders = await GetExternalProviders();
    if (!await CheckSelfRegistrationAsync())
    {
        //if (IsExternalLoginOnly)
        //{
        //    return await OnPostExternalLogin(ExternalLoginScheme);
        //}

        Alerts.Warning(L["SelfRegistrationDisabledMessage"]);
        return Page();
    }

    await TrySetEmailAsync();

    return Page();
}

protected override async Task<bool> CheckSelfRegistrationAsync()
{
    EnableLocalRegister = await SettingProvider.IsTrueAsync(AccountSettingNames.EnableLocalLogin) &&
                          await SettingProvider.IsTrueAsync(AccountSettingNames.IsSelfRegistrationEnabled);

    //if (IsExternalLogin)
    //{
    //    return true;
    //}

    if (!EnableLocalRegister)
    {
        return false;
    }

    return true;
}

Is this a valid approach?

Thanks

Thansk fo reply.

From the issue you indicated I read that LeptonX has 3 layouts: Application, SideMenu and TopMenu.(ABP v.6) I need the Application layout

But now it seems to be no longer available, how can I restore it? https://docs.abp.io/en/commercial/latest/themes/lepton-x/blazor?UI=Blazor#updating-bundles-on-layout-changes

Hi,

If there is an option to prevent a new registration I expect that this will never happen and that the external provider will only be able to log in. How can I change the code to make my solution compliant?

• ABP Framework version: v8.1.0-rc.2
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace: none
• Steps to reproduce the issue:

• Create a new Abp Blazor wasm project
• Disable the "enable self registration" setting in the setting page:
• Implement the code necessary for Azure AD login with external provider:
• Log into the application using a Azure AD user that doesnt have an account on the application
• Notice how the application still prompt you with the register option for the account:

If you press the "register" button it will create a new user, this behavior is not correct because it should only let you login if you already have a user in the application, otherwise it should stop you from registering because of the "self registration" setting.