oh, to answer my own question: https://gitter.im/spring-cloud/spring-cloud-stream?at=5dc1daa6e1c5e915083cc1b3
Hi guys! I need help for my spring boot application. I am working on a backend REST API server. This server exposes a number of resources that must be protected with authentication and authorization rules. The API will be consumed by mobile applications who offer Social Login (Facebook, google) and username and password login. How should I handle this problem authenticating users? I have already used JWT authentication which is fine. But now I need to work with different tokens (coming from Facebook and Google) and I have no idea how to manage them. I read something about OAUTH2 but it is very confusing too me. Thank you in advance !
looks like they also have another video targeted at spring + oauth2 , not sure how good that one is :) https://www.youtube.com/watch?v=TaZqDrwBWwA
@deanstef i tend to think that session or state is not required, but would have to take a look at sources. OTOH https://docs.spring.io/spring-security-oauth2-boot/docs/current/reference/html/boot-features-security-oauth2-resource-server.html does not imply any state, bearer token would be fine, so unless you want to use refresh tokens you should be fine
i am wondering if that is a good practice ?
my goal is to throw group of errors
Hi Team
I am getting error for , this example is from the Spring boot docs. any help appreciated
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'local.server.port' in value "${local.server.port}"
at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:178) ~[spring-core-5.2.3.RELEASE.jar:5.2.3.RELEASE]
at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:124) ~[spring-core-5.2.3.RELEASE.jar:5.2.3.RELEASE]
at org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:236) ~[spring-core-5.2.3.RELEASE.jar:5.2.3.RELEASE]
at org.springframework.core.env.AbstractPropertyResolver.resolveRequiredPlaceholders(AbstractPropertyResolver.java:210) ~[spring-core-5.2.3.RELEASE.jar:5.2.3.RELEASE]
at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.lambda$processProperties$0(PropertySourcesPlaceholderConfigurer.java:175) ~[spring-context-5.2.3.RELEASE.jar:5.2.3.RELEASE]"Test
@SpringBootTest(classes = { TestApplication.class}, webEnvironment = RANDOM_PORT)
public class ELFSpringWebAutoConfigurationTest {
@LocalServerPort
int port;
@Autowired
TestRestTemplate restTemplate;
@Test
void testRestCall() {
assertThat(this.restTemplate.getForObject("http://localhost:" + port + "/",
String.class)).contains("Hello, World");
}
}
@hyginous29 see https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/web/server/LocalServerPort.html
effectively you have
effectively you have
@Value(value="${local.server.port}")
int port;
so you have to define it somehow
ah, my bad, missed
webEnvironment = RANDOM_PORT. disregard my comment
@bclozel Hi Brian, do u have any idea how to implement "store and forward" pattern in Spring boot to store request and retry?
This is a reusable component(lib) which will be included in various microservices to take care of rest requests (webclient) that fail either in upstream or downstream service by storing the request and forwarding once services are available.Initially I was thinking about using resilient operator in webclient(retry) but we are missing the case that upstream fails , so we need to store the request and use callbacks but not sure how to implement this efficiently
@bclozel This is a reusable component(lib) which will be included in various microservices to take care of rest requests (webclient) that fail either in upstream or downstream service by storing the request and forwarding once services are available.Initially I was thinking about using resilient operator in webclient(retry) but we are missing the case that upstream fails , so we need to store the request and use callbacks but not sure how to implement this efficiently
if it's a shared concern amongst services, maybe spring cloud gateway is a better fit here
we already an API gateway so I dont think spring cloud gateway would be an option.
*got
If retry still works on failure (upstream) that would be nice but I dont understand how it works..
if this is a common use case, maybe your API gateway can handle retries?
a failure would be either a response with HTTP 500 status of a failure of upstream(caller) server itself. The requirement to create a shared lib that will be included in different microservices to take care the above. So I dont understand how retry would be possible if caller fails without persisting the request somehow..
*or
a response with HTTP 500 status OR a failure of upstream(caller) server itself.
Let's say a client "A" sends a request to your application "B", and your app sends a request to "C". If "A" is gone, you might get an exception in your app but for sure you won't be able to write to the response. This should not prevent you from sending that request to "C".
Is implementing the store and forward integration pattern and they need to replicate this in microservices
So based on the mentioned pattern the request is saved along with its callback but its quite complicate to replicate this in micro
Basically they are not aware of any othe solution thats why they believe is the only solution thats why am asking if that behavior is feasible using webclient