william-tran / microservice-security

Building OAuth2 secured microservices with Spring Cloud Security. From my talk at SpringOne2GX 2015
https://spring.io/blog/2015/10/19/springone2gx-2015-replay-securing-microservices-with-spring-cloud-security
203 stars 120 forks source link

redirect loop in microsec-openid-sso #2

Open balteo opened 8 years ago

balteo commented 8 years ago

It seems the microsec-openid-sso application is exhibiting a redirect loop issue when run locally and the browser is pointed at this URL: http://localhost:8081/userinfo

william-tran commented 8 years ago

Sorry for the late reply @balteo, I didn't turn on the "watch" setting on this repo until now. I've since fixed it and rebased the fix to make history look like there was no mistake. The issue was with security.require-ssl=true being active when running locally, this should only be active when running in PWS or behind some SSL terminating load balancer. I moved it to the cloud profile to make this work in PWS: https://github.com/william-tran/microservice-security/blob/master/microsec-openid-sso/src/main/resources/application.yml#L46. You could try re-cloning the project and see if that works for you.

balteo commented 8 years ago

Hi Will, Thanks. I will do so.

2016-02-05 16:23 GMT+01:00 Will Tran notifications@github.com:

Sorry for the late reply @balteo https://github.com/balteo, I didn't turn on the "watch" setting on this repo until now. I've since fixed it and rebased the fix to make history look like there was no mistake. The issue was with security.require-ssl=true being active when running locally, this should only be active when running in PWS or behind some SSL terminating load balancer. I moved it to the cloud profile to make this work in PWS: https://github.com/william-tran/microservice-security/blob/master/microsec-openid-sso/src/main/resources/application.yml#L46. You could try re-cloning the project and see if that works for you.

— Reply to this email directly or view it on GitHub https://github.com/william-tran/microservice-security/issues/2#issuecomment-180399457 .