N-WEB | WEB PENETRATION TESTING TOOL | Security Testing library

I have a standalone Blazor WASM site (client), a separate .NET 6 web API (server) with protected endpoints and I'm trying to call MS Graph from the API.

I've read just about every article I could find on the configuration required to make this work and I'm stuck with the incremental consent failing. I get the following error when trying to access a server API which uses MS Graph:

Error acquiring a token for a downstream web API - MsalUiRequiredException message is: AADSTS65001: The user or administrator has not consented to use the application with ID '[redacted]' named '[redacted]'. Send an interactive authorization request for this user and resource.

1. Created AAD app for Web API (server), added secret for Graph configuration, set the app URI and created access_as_user scope under "Expose an API" in AAD.

2. Added the client ID (from the following step) to the knownClientApplications section in the manifest for the server app registration in AAD.

3. For API Permissions I added Graph scopes User.Read, User.Read.All, and Group.Read.All and provided admin consent in the AAD UI.

4. Configured appsettings.json in the API to add the Graph API BaseUrl and above scopes from step 2 along with the correct AzureAD domain, TenantId, ClientId, and ClientSecret values for MSAL to function.

5. Configured MSAL on the server:

I am using Gradle 7.3.3 to build a Spring Boot Application that uses jooq to generate Table, POJO, and Record Classes from a pre-existing database schema. When attempting to upgrade jooqVersion from 3.15.5 to 3.16.0, :generateJooq returns the following error:

I am trying to deploy kubeflow on gcp using official guidelines https://www.kubeflow.org/docs/distributions/gke/deploy/deploy-cli/

I tried three times but it seems there is a problem with endpoints controller. When checked by: kubectl -n kubeflow get all

All pods are running except the

I had installed kube-prometheus-stack from the helm chart repo prometheus-community

hi i m using react with redux. 1 hour before its working perfectly but now getting error TypeScript error in /Users/invest19/Desktop/super admin/super Admin guest /invest19-admin-web/node_modules/redux-thunk/es/index.d.ts(1,13): '=' expected. TS1005

Please help me for resolve this issue

Screenshot

I need to access the theme_display in a Liferay 7.3 Web Content Template.

I tried the following code (from Liferay Portal 6.2 - How to get theme_display in Web Content Template) but it doesn't work (change in Liferay 7.x) I would guess.

I've created a React-based SPA that runs on ASP.NET Core 5.0 but recently encountered an issue after pushing an update with breaking changes to production - users are often seeing errors when trying to access the site because their browser is loading a stale version of the SPA that's incompatible with the changes made to the backend.

Digging into this, it seems like the problem is that index.html is being cached for longer than it should and that I should be configuring it to never be cached, based on what I read in these posts:

• How to avoid caching for create-react-app
• Cache busting with CRA React

I came across a person having a similar issue to mine in the post here and followed that through to this solution. After a bit more digging, I also came across a more comprehensive version of that solution in this Github thread and I've based my current attempt on that.

I found this post that's similar to mine: StaticFileOptions.OnPrepareResponse does not get called for index.html. The difference is that their callback was hit for everything except the the path they were interested in, whereas my callback is never hit at all.

In my application, I've changed my Startup.Configure method to this:

I have very big images in my assets, which slows down the site by a lot for slower networks. (you can read more about the topic on this lighthouse linked page)

• I would like to compress them at build time (ng build --prod).
• For local development, it is irrelevant (ng serve).
• Optimally I would like to generate multiple versions for different screen sizes (example.jpg → should become: example_x265.jpg, example_x128.jpg, ...)

The most promising guide I have found for that is this one here, which describes how to use the imagemin package in combination with the ngx-build-plus package.

Unfortunately, after following the tutorial, I get the following error:

My React app is using Webpack + Babel. When I compile in development everything works perfectly well.

When I bundle for production ("npm run build") and upload the bundle in prod, an error appear in the console:

Why? I found a similar question but didn't find an answer : related stackoverflow question

Here's my webpack.prod.js config: