Closed ar-bella-jeong closed 10 months ago
Hi @ar-bella-jeong ,
A few questions for you if you don't mind.
Thanks
Hi @onobc
I answered you asked that as below.
2.. How are you installing Dataflow into K8s? For previous version, I used bitnami helm package. but now in case of 2.11.0-RC1, I made k8s manifests.
As I said, this issue is about the permission problem of /schema/versions
which is new api for boot3 compability.
now, I added the api into spring.cloud.dataflow.security.authorization.permit-all-paths
prop so that showing boot versions in new application page. it works well.
As a result, I think we need to set the role or add into permit-all-paths for the api.
Thanks.
/schema/versions is a new controller. The security role definition needs to be added to the default list.
Description: I'm using
springcloud/spring-cloud-dataflow-server:2.11.0-RC1
to test dataflow in k8s 1.27. I also use keycloak to use oauth, but when I try to add application, boot app versions are not displayed. so I checked/schema/versions
api responses '403'. I supposed that spring security setting in dataflow doens't have not only role of the api, but also isn't set in permit-all-paths.Release versions: spring-cloud-dataflow-server:2.11.0-RC1
Steps to reproduce:
/schema/versions
api responses '403'.