對SpringCloud做一次簡單的問題總結。

application.yml 和 bootstrap.yml 有何區別？

I have just asked the Spring Cloud guys and thought I should share the info I have here.

bootstrap.yml is loaded before application.yml.

It is typically used for the following:

when using Spring Cloud Config Server, you should specify spring.application.name and spring.cloud.config.server.git.uri inside bootstrap.yml

some encryption/decryption information

Technically, bootstrap.yml is loaded by a parent Spring ApplicationContext. That parent ApplicationContext is loaded before the one that uses application.yml.

bootstrap.yml在application.yml之前加載。

通常用于以下幾方面：

在使用 Spring Cloud Config Server時，應在bootstrap.yml中指定spring.application.name和spring.cloud.config.server.git.uri。

一些加密/解密信息。

技術方面，bootstrap.yml由父SpringApplicationContext加載。父ApplicationContext在使用application.yml之前加載。

Spring Eureka服務器在客戶端url中找不到 Context-path

If your Eureka client is setup via Spring's @EnableEurekaClient, then the client will default the health check and status check to /health and /info respectively. (These paths may be the default values beyond the Spring @EnableEurekaClient setup, but I am unfamiliar with those at this point in time).

You can override these defaults by setting the following properties:

eureka.instance.statusPageUrlPath

eureka.instance.healthCheckUrlPath

The Spring Cloud Documentation contains this information, plus much more.

如果你的Eureka客戶端是通過Spring的@EnableEurekaClient設置的，那么客戶端將分別將健康檢查(health check)和狀態檢查(status check)默認為/health 和 /info。

你可以通過設置以下屬性來覆蓋這些默認值：

eureka.instance.statusPageUrlPath

eureka.instance.healthCheckUrlPath

在eureka環境下如何正確設置spring boot admin客戶端的 management.context-path

On the client:

eureka:

instance:

metadata-map:

management.context-path: ${management.context-path}

As described in the docs:

If you want to customize the default conversion of services you can either add health.path, management.port and/or mangament.context-path entries to the services metadata.

在客戶端增加配置：

eureka:

instance:

metadata-map:

management.context-path: ${management.context-path}

如 文檔中所述：

如果要自動已服務的 default conversion，可以將health.path、management.port和/或management.context-path條目添加到service metada中。

Spring Boot 升級 1.5.x(從 1.3.x)跳轉 login 問題解決

Ok, I got it now.

@Cleto Gadelha pointed me very usefull info.

However I think release note is pretty unclear or miss some information. Beside that OAuth2 resource filter is changed from 3 to SecurityProperties.ACCESS_OVERRIDE_ORDER - 1, crucial information is that default WebSecurityConfigurerAdapter order is 100 (source).

So in before release 1.5.x OAuth2 resource server order was 3 which had higher priority then WebSecurityConfigurerAdapter.

After release 1.5.x OAuth2 resource server order is set to SecurityProperties.ACCESS_OVERRIDE_ORDER - 1

(it is Integer.MAX_VALUE - 8 I think) which has now definitely lower priority then basic WebSecurityConfigurerAdapter order.

That's why login page appears for me after migrate from 1.4.x to 1.5.x

So, more elegant and java-like style solution is to set @Order(SecurityProperties.ACCESS_OVERRIDE_ORDER) on WebSecurityConfigurerAdapter class

主要由于在1.5.x版本之前，OAuth2資源服務器Order為3，其優先級高于WebSecurityConfigurerAdapter。發布1.5.x后，OAuth2資源服務器順序設置為SecurityProperties.ACCESS_OVERRIDE_ORDER - 1(我認為是Integer.MAX_VALUE - 8)，他的優先級現在肯定低于基本的WebSecurityConfigurerAdapter順序。

這就是為什么從1.4.x遷移到1.5.x后，我會看到登陸頁面的原因。

因此，更優雅和類似Java的樣式解決方案是在WebSecurityConfigurerAdapter類上設置@Order(SecurityProperties.ACCESS_OVERRIDE_ORDER)。

關于 Spring Boot 權限管理的一些文檔

多個 ResourceService 共享一個 AuthorizationService，在多個服務的Controller 間相互調用(fegin)進行授權驗證，Scope 丟失

注入其他項目中的feignClient出現無法被scan到(注入失敗)

總結

以上是生活随笔為你收集整理的java发邮件无主题,使用SpringCloud过程中遇到的一些问题的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。