unauthenticated swagger-ui on- server-port and proper security filter integration into Spring Security #163
@ -54,11 +54,6 @@ spring:
|
||||
liquibase:
|
||||
contexts: ${spring.profiles.active}
|
||||
|
||||
# keep this in sync with test/.../application.yml
|
||||
springdoc:
|
||||
# SwaggerUI must run on the same port as the API itself, otherwise CORS will block accessing the API
|
||||
x-use-management-port: false
|
||||
|
||||
hsadminng:
|
||||
postgres:
|
||||
leakproof:
|
||||
|
@ -39,12 +39,6 @@ spring:
|
||||
change-log: classpath:/db/changelog/db.changelog-master.yaml
|
||||
contexts: tc,test,dev,pg_stat_statements
|
||||
|
||||
# keep this in sync with main/.../application.yml
|
||||
springdoc:
|
||||
# SwaggerUI must run on the same port as the API itself, otherwise CORS will block accessing the API
|
||||
x-use-management-port: false
|
||||
|
||||
|
||||
logging:
|
||||
level:
|
||||
liquibase: WARN
|
||||
|
Loading…
x
Reference in New Issue
Block a user