You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cloud SDK for Java doesn't support service credentials of the SAP BTP connectivity service (connectivity plan proxy) out-of-the-box. The documentation describes required changes.
However, the documentation doesn't seem to be complete. The following 3 properties (example values) need to be added:
This approach doesn't scale for app development. Instead of this the Cloud SDK should recognize the different configuration structure and has a way to provide the onpremise_proxy_host and onpremise_proxy_http_port without the need to modify a generated secret. For example using environment variables or using a separate secret that can be statically setup in the application namespace without dependency to the clientid and secret that is generated by the service instance.
uwe-klinger
changed the title
Support Connectivity Service Secret on Kubernetes out-of-the-box
Support Connectivity Service Secret on Kubernetes out-of-the-box (Java)
Jan 27, 2022
Sorry, I think this thread was overlooked somehow. In the meanwhile the on-premise handling on K8S changed with the release of the transparent proxy. The Cloud SDK documentation has been updated to describe how to use Cloud SDK with the transparent proxy. That way no manual adjustment of the secret should be needed anymore.
Issue Description
Important information:
The Cloud SDK for Java doesn't support service credentials of the SAP BTP connectivity service (
connectivity
planproxy
) out-of-the-box. The documentation describes required changes.However, the documentation doesn't seem to be complete. The following 3 properties (example values) need to be added:
This approach doesn't scale for app development. Instead of this the Cloud SDK should recognize the different configuration structure and has a way to provide the
onpremise_proxy_host
andonpremise_proxy_http_port
without the need to modify a generated secret. For example using environment variables or using a separate secret that can be statically setup in the application namespace without dependency to the clientid and secret that is generated by the service instance.I reported the same issue for Cloud SDK Java: SAP/cloud-sdk-js#2024
Impact / Priority
Project Details
Checklist
The text was updated successfully, but these errors were encountered: