Closed imaxkhan closed 1 year ago
This is a really old example. It uses JHipster 5.4.2, whereas 7.9.3 is the latest version. I recently created an example that uses JHipster 8 with Spring Boot 3. While JHipster 8 is not released yet, I used the main
branch, which will eventually become JHipster 8.
https://github.com/oktadev/auth0-java-microservices-examples/blob/main/reactive-jhipster/demo.adoc
i cant move to new jhipster already. but did u have same problem? token is in my session and i have access to it but when i add it manually not working again..but i believe this interceptor should work..its two weeks im working on it
I'm not sure I understand your issue. Can you please provide the steps to reproduce your problem using this example?
I didn't experience any issues when I created this example 5 years ago.
yes right now im connecting ur gateway to spring authorization server. i added one route to gateway such as /product now after successful login i wanna call product service with gateway . now i can see that access token is present in defaultOauth2Context... but TokenRelayRequestInterceptor class never being called to relay the token to product service.. so i face 401 unauthorized from product service which expect bearer access token from gateway
also
@Bean
public FilterRegistrationBean
not working
When you say Spring Authorization Server, are you saying this project? If so, I find it strange that you can use a new thing like Spring Authorization Server, but are stuck on an old version of JHipster.
Since you're not using this example with Okta, I'd recommend posting your question on Stack Overflow. That way, more people will see it, including Spring Authorization Server experts.
well its federated authorization server which is connected to azure b2c and we have one front-end which is written by jhipster gateway... by the way yes u are right tnx for ur time...
You're welcome. I'll close this issue now.
hi im using ur sample but requestInterceptor not being called to relay token