Spring-Boot-2 | Spring Boot 2.x examples | Object-Relational Mapping library

This problem's caused by a bug in Springfox. It's making an assumption about how Spring MVC is set up that doesn't always hold true. Specifically, it's assuming that MVC's path matching will use the Ant-based path matcher and not the PathPattern-based matcher. PathPattern-based matching has been an option for some time now and is the default as of Spring Boot 2.6.

As described in Spring Boot 2.6's release notes, you can restore the configuration that Springfox assumes will be used by setting spring.mvc.pathmatch.matching-strategy to ant-path-matcher in your application.properties file. Note that this will only work if you are not using Spring Boot's Actuator. The Actuator always uses PathPattern-based parsing, irrespective of the configured matching-strategy. A change to Springfox will be required if you want to use it with the Actuator in Spring Boot 2.6 and later.

It seems the issue lies in the fact with how you try to access your DB in gitlab.

When you add the mysql service

I've tried your example:

consider add xml lib in dependency, as:

You can try setting prePostEnabled = false and then removing any authentication filters in WebSecurityConfigurerAdapter implementation with something like

Please note that Spring Cloud Config Server client will build the full path to your application's profile specific configuration for you. Therefore, you should only provide the base URL in bootstrap.properties. In your case this would be probable some like this:

I tried to replicate this in my local machine and here the solution.

You have to create your own dilect by extending org.hibernate.dialect

Your CurrencyExchange_Logic class has two constructors: the required args constructor, which has parameters corresponding to the 3 final fields, and the all args constructor, with parameters corresponding to those 3 fields as well as start and end.

When you only have one constructor defined, Spring knows how to implicitly choose it for injection. However, when you have more than one, you have to tell it which one you want it to use, using the @Autowired or @Inject annotation.

I would guess you want Spring to use the required args constructor, as I doubt Spring has any way of knowing how to resolve the start or end fields. This can be done in lombok (@RequiredArgsConstructor(onConstructor_ = @Autowired)), or by just explicitly writing the constructor yourself and annotating it. Note you could also get rid of the all args constructor, if you don't need it, and Spring's implicit constructor injection should "just work."

OK. So after spending lot of times I got solutions.

First of all, there is nothing wrong with the code snippet mentioned above, reason of this error is-

Accroding to spring security doc under section 18.4.4, In case of active directory search, after authenticating the user successfully, the LdapAuthenticationProvider will attempt to load a set of authorities for the user by calling the configured LdapAuthoritiesPopulator bean. The DefaultLdapAuthoritiesPopulator is an implementation which will load the authorities by searching the directory for groups of which the user is a member (typically these will be groupOfNames or groupOfUniqueNames entries in the directory).

If you want to use LDAP only for authentication, but load the authorities from a difference source (such as a database) then you can provide your own implementation of this interface and inject that instead.

But I was ignoring the authorities which was returning after successfull authentication of the user, that is why I was getting this error.

There are few ways to solve the problem:

1st Way: using Context.REFERRAL to follow

Disadvantage: it will take lot of time to follow the referral and authenticate user

2nd Way: By implementing LdapAuthoritiesPopulator

CustomAuthoritiesPopulator.java