Closed gberche-orange closed 4 years ago
Osb-cmdb does not yet provide such feature
Reproduced on version 1.0
Given a brokered service instance with guid brokered_guid is backed by backend service instance with guid backend-guid
brokered_guid
backend-guid
And osb-cmdb is exposed at osb-cmdb-0.redacted_domain
And osb-cmdb is configured with osb-tenant Oauth and permission endpoint
When traffic is sent to the route service endpoint https://osb-cmdb-0.redacted_domain/route_service/`brokered_guid`
Then incoming user request is authenticated against the tenant Oauth server
And the incoming user request is authorized against the tenant endpoint with brokered_guid as param
And if authenticated proxifies traffic to specified routed url in X-CF-Forwarded-Url header, otherwises returns a 401 error with a message explaining the authN failure.
X-CF-Forwarded-Url
And the incoming user is authorized
Expected behavior
Observed behavior
Osb-cmdb does not yet provide such feature
Affected release
Reproduced on version 1.0
Acceptance test scenario
Given a brokered service instance with guid
brokered_guid
is backed by backend service instance with guidbackend-guid
And osb-cmdb is exposed at osb-cmdb-0.redacted_domain
And osb-cmdb is configured with osb-tenant Oauth and permission endpoint
When traffic is sent to the route service endpoint https://osb-cmdb-0.redacted_domain/route_service/`brokered_guid`
Then incoming user request is authenticated against the tenant Oauth server
And the incoming user request is authorized against the tenant endpoint with
brokered_guid
as paramAnd if authenticated proxifies traffic to specified routed url in
X-CF-Forwarded-Url
header, otherwises returns a 401 error with a message explaining the authN failure.And the incoming user is authorized