Amrut Prabhu

Hey @uniquejava , I think the redirect URL has to be of this format ` "{baseUrl}/{action}/oauth2/code/{registrationId}";` you can have a look at this class here: `CommonOAuth2Provider`. Try changing it. see...

Maybe I can backport this change from 3.0. I'll try for first secrets manager then look into the parameter store. can you guide me through the change for 3.0 if...

Let me give see if I understand this right. I see the `CredentialsProperties` is `io.awspring.cloud.autoconfigure.context.properties.AwsCredentialsProperties` in 2.4.x branch, which is present in the `Spring-cloud-aws-autoconfigure` module. Now I have to use...

Just my second thought about this change. I don't think we could create the provider in the `Spring-cloud-aws-autoconfigure` module and not may be the `Spring-cloud-starter-aws-secret-manager`. We then could fetch it...

Hey @paidisettyv , Sorry for the late reply. 1. To run `docker-compose.yaml` you need to run ` docker compose up` command. Make sure Docker is installed on your system. 2....

I think you are not running the docker-compose file. The application is not able to communicate with Jaeger.

If you are running the docker compose file, can you try accessing the URL http://localhost:16686/. It should open the Jaeger UI.

You can read also about it here: https://refactorfirst.com/distributed-tracing-with-opentelemetry-jaeger-in-spring-boot

I quickly checked. Cloned the repo again and ran it with docker compose and it all works fine. Not sure why it's not communicating with the Jaeger in your case....

Is the Jaeger image 1.12 ? .. like what I see in the comments? You will have to use the latest version of `jaegertracing/all-in-one` Because the opentelemetry support is after...