cryptoutil | java crypto util , include desEEECbc , AES192/256 | Encryption library

Actually the problem is coming from the REST component. He set HeaderFilter which override the other setted filter in HTTP component. REST component can not set HeaderFilterStrategy and always use default one. I was start to use only http component with setted mine customised filter instead rest and now can transfer deleted headers from DefaultHeaderFilterStrategy.

I replace it

Yes, you can force users to use two factor authentication with MSAL angular. Your angular configuration is looking OK. Now you need to recheck your azure configurations. You can configure your settings here.

1. Check if you have defined module version (v2)

   module github.com/micromdm/scep/v2 @ /home/pi/go/scep/go.mod

2. change the path to the module to be relative, in this case, it works.

update 1: I see you did, but that only option I got in my mind.

update 2: found a small solution.

I solved this by adding the NODE_ENV check on my factories and seeds files to avoid getting files in dist and src.

The problem was that I am working in development environment. The entities were found in the dist directory instead of factories and seeds who were found in the src instead of the dist folder.

The solution was to apply the process.env.NODE_ENV check on the factories and seeds too:

I figure it out what going on. My XMLReader method wasn't working properly. Yes it was returning string exactly but missing some point in bytes. So I change it a little.

First I read and convert to Doc file

state is what you should use.

https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-js-pass-custom-state-authentication-request

The state parameter, as defined by OAuth 2.0, is included in an authentication request and is also returned in the token response to prevent cross-site request forgery attacks. By default, Microsoft Authentication Library for JavaScript (MSAL.js) passes a randomly generated unique state parameter value in the authentication requests.

The state parameter can also be used to encode information of the app's state before redirect. You can pass the user's state in the app, such as the page or view they were on, as input to this parameter. The MSAL.js library allows you to pass your custom state as state parameter in the Request object

The passed in state is appended to the unique GUID set by MSAL.js when sending the request. When the response is returned, MSAL.js checks for a state match and then returns the custom passed in state in the Response object as accountState.

Make sure you have the "java cryptography extension (jce) unlimited strength jurisdiction policy files 8" from here. See this for instructions.

In general, when you do not see an increase by multi threading, it is because your task is not CPU limited or large enough to offset the overhead.

In your example, i.e.:

selectedApi.GetTickerAsync(symbol);

This can hae 2 reasons:

1: Looking up the ticker is brutally fast and it should not be an async to start with. I.e. when you look it up in a dictionary.

2: This is running via a http connection where the runtime is LIMITING THE NUMBER OF CONCURRENT CALLS. Regardless how many tasks you open, it will not use more than 4 at the same time.

Oh, and 3: you think async is using threads. It is not. It is particularly not the case in a codel ike this:

await selectedApi.GetTickerAsync(symbol);

Where you basically IMMEDIATELY WAIT FOR THE RESULT. There is no multi threading involved here at all.

foreach (IExchangeAPI selectedApi in selectedApis) { if (exchangeSymbols.TryGetValue(selectedApi.Name, out symbol)) { ticker = await selectedApi.GetTickerAsync(symbol); } }

This is linear non threaded code using an async interface to not block the current thread while the (likely expensive IO) operation is in place. It starts one, THEN WAITS FOR THE RESULT. No 2 queries ever start at the same time.

If you want a possible (just as example) more scalable way:

• In the foreach, do not await but add the task to a list of tasks.
• Then start await once all the tasks have started. Likein a 2nd loop.

WAY not perfect, but at least the runtime has a CHANCE to do multiple lookups at the same time. Your await makes sure that you essentially run single threaded code, except async, so your thread goes back into the pool (and is not waiting for results), increasing your scalability - an item possibly not relevant in this case and definitely not measured in your test.