Activities of "joe@tronactive.com"

That isn't going to find package level vulnerabilities. Completely different. Also, for code vulnerabilities, OWASP could catch a lot of those. But SonarCloud will find them much quicker and will point directly to the code that is a vulnerability. OWASP wouldn't do that. Just to a basic API Endpoint level. Also, SonarCloud and Mend can easily be put into the build pipeline to check during each build. Or on a schedule.

Alper, you may want to consider using MEND (formerly WhiteSource, www.mend.io) to show vulnerabilities reported in .NET and NPM packages; it also tells you what versions the vulnerabilities have been fixed in. The second one you may want to look into is Sonarcloud (sonarcloud.io) which is incredible for finding security vulnerabilities in the actual source code.

My work uses both for compliance reasons, and they work fantastically to keep the codebase as secure as possible before deploying to the server.

Awesome. Thank you very much. I appreciate the help.

Yes that is correct. We are using Blazor Server version.

How do I update those. I can't find the correct Package.json file

• ABP Framework version: v6.0.2
• UI type:Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

For our project we scan our source code during the pipeline build with the service MEND formerly known as WhiteSource. I use LeptonX in our project and the scan is finding a lot of javascript library vulnerabilities that the security team needs me to fix ASAP. The problem I see is, I don't seem to have much control over these files and how I can update them since they are apart of the LeptonX code base. Does anyone have any ideas of what I can do?

I am having the same issues. Any ideas?

Does anyone have any ideas?

• ABP Framework version: v6.0.1
• UI type: Blazor Server
• DB provider: EF Core

I am trying to add some basic components to the top toolbar in the LeptonX theme. I am just trying to start by adding a drop-down but cannot get it to show up. I added my own version of SideMenuLayout.Razor named MySideMenuLayout which inherits from SideMenuLayout. I think it has to do with where I am placing the files. I tried two places. First one was Themes\LeptonX\Components\ApplicationLayout. Second place was Components\ApplicationLayout\MySideMenuLayout.razor and MySideMenuLayout.razor.

Here is the razor file. 

@using Volo.Abp.AspNetCore.Mvc.UI.Components.LayoutHook

<div class="lpx-scroll-container ps">
	<div id="lpx-wrapper">
		<MainHeader />

		<div class="lpx-content-container">
			<div class="lpx-topbar-container">
                <div class="lpx-topbar">
                    <MainHeaderBranding />
                    <p>Select a Customer</p>
                    <Dropdown>
                        <DropdownToggle Color="Color.Primary">
                            Dropdown
                        </DropdownToggle>
                        <DropdownMenu>
                            <DropdownItem>UAT Customer</DropdownItem>
                        </DropdownMenu>
                    </Dropdown>
                    <Breadcrumbs/>
                </div>
			</div>
			<div class="lpx-content-wrapper">
				<div class="lpx-content">
					<ContentToolbar />
					<PageAlert />
                    @typeof(LayoutHooks.Body)
                    <DynamicLayoutComponent />
					<UiMessageAlert />
					<UiNotificationAlert />
				</div>
			</div>
		</div>

		<MobileNavbar />

		<div class="lpx-toolbar-container">
			<MainHeaderToolbar />
		</div>
	</div>
</div>

Here is the cs file

using System.Threading.Tasks;
using Microsoft.AspNetCore.Components;
using Microsoft.Extensions.Options;
using Microsoft.JSInterop;
using Volo.Abp.AspNetCore.Components.Web;
using Volo.Abp.DependencyInjection;
using Volo.Abp.LeptonX.Shared;


namespace Cure8.Blazor.Components.ApplicationLayout;

[ExposeServices(typeof(SideMenuLayout))]
[Dependency(ReplaceServices = true)]
public partial class SideMenuLayout : Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.SideMenuLayout
{

}

Any updates on this?

The HandleErrorAsync(ex); is only in the BLazor component though. The issue I am having is getting the error from the server and actually getting all the way to the component. It is getting lost somewhere and not making it to the client to be handled by the HandleErrorAsync method.