Open bindian0509 opened 1 year ago
Half of the problem seems to be solved by changing application.yml format of supplying username and password,
Now with spring security, these application properties can be accessed via spring_cloud_user
from the browser.
but somehow the client is not able to authenticate with the same user mentioned in twitter-to-kafka-app's application.yml
Correct format
spring
security:
user: // this was missing
name: spring_cloud_user
password: ENC(<encrypted-value>)
Figured out that it was not a problem of spring security rather a problem with jasypt not loading with twitter to kafka application, when I use plain text value of password in application.yml it works fine. Looking more to understand what is causing a problem here to not let jasypt get involved in launching the main application.
Getting following exception in running the twitter to kafka service application -