java-jwt | Java implementation of JSON Web Token | Authentication library

If this is a local environment, you don't need to configure Spring, instead you modify angular configuration.

Create a file proxy.conf.json in your project's src/ folder.

Add the following content to the new proxy file:

-- Solved --

So I ran my default project on Spring Boot 2.7.0 and 2.6.3 on my test project. When I changed to 2.6.3 on default, it ran. So it seems like the latest GrahpQL isn't fully compatible with Spring Boot 2.7.0 yet. Which might be obvious because it was released in the last month.

I was facing the very same problem with azure dependencies last few days. Upgrading spring-boot-starter-parent to version 2.5.5 fixed it for me.

For IntelliJ Idea, when using Lombok you have to enable annotation processing.

• Preferences (Ctrl + Alt + S)
  • Build, Execution, Deployment
    • Compiler
      • Annotation Processors
        • Enable annotation processing

If the problem still persist:

Add version 1.18.16.

I found a solution for my problem. The following steps solved my issue.

1. Add the dependency without system and ... In my case I had to add:

It seems that you have flyway dependency in your pom. When using @SpringbootTest, It will initialize the whole application context. According to the Springboot Autoconfigure mechanism, the application detects the Flyway module and tries to create a bean named flyway:

Error creating bean with name 'flyway'

And then when constructing the flyway bean, the flyway Factory needs a datasource bean.

I cannot reproduce the problem because IDEA does not find the Lombok setters. Even when delegating build actions before run to Maven, I get NoSuchMethodError: '...TestEntity.setCode(java.lang.String)'. Next, I am going to try without Lombok. Please note that Lombok and AspectJ do not play nice with each other, see my answer here. Alternatively, you could also make sure that Maven does either of these:

1. First build with Javac + Lombok, then apply AspectJ binary weaving in a second step, all in one module.
2. Similar to above, but do the first build step in module A and the second one in a separate module B. Then you have an unwoven and a woven artifact, which you can both use according to your preferences. For example, you could also use the unwoven one and apply transaction aspects via load-time weaving (LTW) while starting the application. See my other answer here for both approaches #1 and #2.
3. Delombok the source code build the generated sources with the AspectJ compiler in a second build step.

I generated constructors, getters and setters in the IDE instead of using Lombok. Now the project compiles in both IDE and Maven. It behaves exactly as it should. With @Transactional, 0 entities are created, without it 2.

I am not sure if Lombok vs. AspectJ really is the problem due to non-compileability when using Lombok annotations, but it should be easy enough to try without Lombok for you. If it works in your context, too, we found the culprit and can think about implementing one of the 3 approaches mentioned above. Then you can tell me if you have any difficulty in doing so.

Update: I created the two-module version - Javac + Lombok, then Aspect weaving - for you in my fork and also issued pull request #1. I also improved testability a bit. See if that works for you.

Caveat: You cannot simply run DemoApplication from the application-lombok module, because that module is still unwoven and will not show transactional behaviour. But you can simply change the classpath for the run config to the application-aspectj module:

Update: As we found out in the comment section of the other answer, in addition to the problematic Lombok vs. AspectJ compiler configuration, the OP also simply had a problem with his IDE: Using IntelliJ IDEA Community Edition, he was first unaware of, then unable to install the AspectJ plugin, which means that IDEA does not know antyhing about the AspectJ compiler and simply overwrites anything which might have been compiled by AspectJ Maven before with plain Java classes. Therefore, transactional aspects do not work either, unless

• either pre-run compilation is disabled and mvn compile started as an additional pre-build step for the corresponding run configuration,
• or all build actions for the project are being delegated to Maven via configuration,
• the OP buys a licence of IDEA Ultimate and installs the AspectJ plugin.

You are trying to validate an access token meant for Microsoft Graph API. You should not do that, primarily because it is not meant for your app. They use something a bit different for signing and you can't use the same methods to validate Graph API tokens.

When acquiring tokens, make sure to use scopes defined by your application to receive a token for your app. That one you should be able to validate. If you also need to call MS Graph API, then you need to acquire two tokens.

I managed this problem creating a new repo on CodeArtifact. I suppose that something was wrong in the repo I was managing, but I didn't changed any configuration.