javadevjournal / javadevjournal Goto Github PK

Hi and thank you for great article. The note at the bottom about Hikari switch in Springboot 2.0, all I had to do is rename

spring.datasource.url=....

to:

spring.datasource.jdbc-url=....

Given that it is such a simple change, I think it would significantly improve your article if you add that solution instead of having the comment with a url to another site. The url document does have that information as well; however, it is little bit hidden:

Just a suggestion, much appreciated for the article.

In the article https://www.javadevjournal.com/spring-security/spring-security-multiple-authentication-providers/, I would except to see an implementeation showing how multiple auth providers can be added to an app. For example:

1. LDAP auth provider
2. Oath auth provider
3. LoginForm auth provider
4. DB auth provider
5. ...

, however, all I see is article talking about multiple auth providers but using a single user based auth provider (DB). It does not show at all nor provide example where we have multiple authentication providers. It provides a single CustomAuthenticationProvider using UserDetailsService to get user details from database.
Same thing is with the provided code on this github

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
[2021-06-09 18:03:28.688] - 428
Serious [main] --- org.springframework.boot.SpringApplication: Application run failed
org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.context.ApplicationContextException: Unable to start ServletWebServerApplicationContext due to missing ServletWebServerFactory bean.
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:157)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:540)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
at com.javadevjournal.SpringBootCustomMessageSourceApplication.main(SpringBootCustomMessageSourceApplication.java:21)
Caused by: org.springframework.context.ApplicationContextException: Unable to start ServletWebServerApplicationContext due to missing ServletWebServerFactory bean.
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.getWebServerFactory(ServletWebServerApplicationContext.java:206)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:180)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:154)
... 8 more

Develop Eureka Server

Develop Eureka Client1

Hey, thanks for your very helpful tutorial. I was looking in the CustomAuthenticationFilter and wondering wheather you're actually using your custom UsernamePasswordAuthenticationToken. I appears you're just calling the the parents attemptAuthentication mehtod without passing the custom Token to an authentication Manager. Maybe I'm missing something.

When including the de.codecentric:spring-boot-admin-starter-client dependency in my Spring Boot application, I encounter issues with connecting to Jedis, resulting in connection failures. However, upon removing this dependency, the Jedis connection functions as expected.

Expected Behavior:
The inclusion of the spring-boot-admin-starter-client dependency should not interfere with the ability to establish connections to Jedis servers within the Spring Boot application.

Actual Behavior:
Adding the spring-boot-admin-starter-client dependency leads to Jedis connection failures or errors, hindering the normal operation of the Spring Boot application.

Additional Information:

Version of spring-boot-admin-starter-client being used: 3.2.1
Version of Jedis client being used:

Dear Author,

I use spring-boot-starter-mail and implement EmailService in the similar way (I just add error type, which can be throwed by the sendSimpleEmail method)
Service is being called from the RestController:
@GetMapping("/email") public @ResponseBody Object email() { try { mailer.sendSimpleEmail("[email protected]", "Test Subject", "Test message"); // <-- hangs up here return ResponseEntity.ok(new GenericResponse("OK")); } catch (Exception ex) { return ResponseEntity.badRequest().body(new GenericResponse(ex.getMessage())); } }
When the endpoint is called by Postman, it hangs up and returns nothing

Hi,
I define bean in spring-config.xml in order to have it istantiated once use method verifyTotp. Here the definition inside the xml:

<bean id="codeVerifier" class="dev.samstevens.totp.code.DefaultCodeVerifier" />

On the server startup I receive error in the logs:

org.springframework.beans.BeanInstantiationException: Failed to instantiate [dev.samstevens.totp.code.DefaultCodeVerifier]: No default constructor found; nested exception is java.lang.NoSuchMethodException: dev.samstevens.totp.code.DefaultCodeVerifier.()

Which workaround/method you suggest to follow?

Thanks in advance for answers.