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 static-creds-broker is designed for returning credentials of existing services already provisionned (e.g. an http cache service configured for a given application). Such existing services might already expose UIs to manage the service.
The static-creds-broker responsibility could therefore be to bridge authentication between CF UAA-based authentication and the remote existing service authentication.
The remote service authentication could be expecting:
HTTP basic auth (auth) + HTTPS (confidentiality)
The static-creds broker would then act as an HTTP gateway between the app team identitied in CF and the legacy service UI.
Possible yml expression:
# security properties could be removed, if it's configured in the manifest.yml through environment variable SECURITY_USER_NAME and SECURITY_USER_PASSWORDsecurity:
user:
password: <broker_password>services:
CACHE:
DESCRIPTION: My existing serviceMETADATA:
LONGDESCRIPTION: A long description for my serviceCREDENTIALS:
HOSTNAME: http://company.comDASHBOARD_GATEWAY:
url: https://login:[email protected]PLAN:
PLAN1:
NAME: cache1CREDENTIALS:
URI: http://mydev-api.org/cache1ACCESS_KEY: AZERT23456664DFDSFSDFDSFDASHBOARD_GATEWAY:
url: https://login:[email protected]/cache1HOSTNAME: http://prod.company.comPLAN2:
NAME: cache2CREDENTIALS:
URI: http://mydev-api.org/cache2ACCESS_KEY: SFFGSFZSFDASHBOARD_GATEWAY:
url: https://login:[email protected]/cache2HOSTNAME: http://prod.company.com
In terms of supporting flexible authentication and request mapping the spring-cloud-netflix routing could be a powerfull approachn with rich, expressive routing, filtering ... rules that would be embbeded in the static-creds subtree as sub elements of the DASHBOARD_GATEWAY part.
The text was updated successfully, but these errors were encountered:
The static-creds-broker is designed for returning credentials of existing services already provisionned (e.g. an http cache service configured for a given application). Such existing services might already expose UIs to manage the service.
The static-creds-broker responsibility could therefore be to bridge authentication between CF UAA-based authentication and the remote existing service authentication.
The remote service authentication could be expecting:
The static-creds broker would then act as an HTTP gateway between the app team identitied in CF and the legacy service UI.
Possible yml expression:
In terms of supporting flexible authentication and request mapping the spring-cloud-netflix routing could be a powerfull approachn with rich, expressive routing, filtering ... rules that would be embbeded in the static-creds subtree as sub elements of the DASHBOARD_GATEWAY part.
The text was updated successfully, but these errors were encountered: