Angular-Client | Keep Current Web UI - Where users can view and rate | Frontend Framework library

stdin_open: true

do the trick

I found the answer in Why does openapi-generator not create a package.json with typescript-angular?.

I had to set tmsClientRest for openapi-generator-maven-plugin:

This is an issue with the typescript-angular generator:

https://github.com/OpenAPITools/openapi-generator/issues/4404

A Pull Request has been created to fix this issue, I advise you to watch it:

https://github.com/OpenAPITools/openapi-generator/pull/4407

In the meantime you can try to solve the issue similarly to the @PageableAsQueryParam annotation available in springdoc-openapi-data-rest. That is, you can use @Parameters on your Spring controller method and @Parameter(hidden = true) on the method parameter itself to redefine the documentation manually.

It sucks, but it's the best solution until the Pull Request goes through.

In case of the method you wrote, the fix would be fairly simple, just add @PageableAsQueryParam and @Parameter(hidden = true):

If you are using angular-cli, you would have to run ng serve --host 0.0.0.0 in order for angular cli to expose the angular-life-server. However it is not recommended to do this for production purposes, as the angular-life server is not fully reviewed for security concerns, but only meant as a development tool. To deploy you angular app for production, it would be best to do a production build (ng build --prod) and deploy the result inside e.g. a nginx-container.

I have been looking into this for about 2 days, there were multiple issues that i had going on here. The first was that the MVC project that I was working with needed a few things to happen.

I needed to add a bit to WebConfig file:

CouchDB and PouchDB use the same replication protocol. There are some optimizations introduced in CouchDB 2.x, but PouchDB 7 will still be able to sync without a problem in CouchDB 1.6.

However, you absolutely should not use CouchDB 1.6!! 1.6 had some very serious security flaws, which can essentially allow anyone to execute arbitrary code on your server. These were fixed in 1.7 and later. So please upgrade to at least 1.7.1 immediately!

I should have listened to @Suresh-Kumar-Ariya from the beginning but that subject was a bit confusing form me.

@user184994 also helped me after reading this post for the 5th time that I really should check my providers since it's a problem only detected when I use AOT.

so anyhow I use Document as a provider, I read somewhere that I needed to use that in order to use document which was false. removing it solved the problem

thanks all

Inside a controller action that is protected with an [Authorize] attribute you can simply get claims directly from the ClaimsPrinciple, without having to go through a manual discovery client. The claims principle is handily aliased simply with User inside your controllers.

I'm asking also because I have seen anothers using

string userId = User.Claims.FirstOrDefault(c => c.Type == ClaimTypes.NameIdentifier).Value;

that is more straightforward but doesn't seems to fit with reference tokens.

It works just fine with reference tokens. You should have no problems accessing the sub claim.

EDIT: As I mentioned in a comment below, I tend to use the standard JwtClaimTypes and create some extension methods on the ClaimsPrinciple, such as: