Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GET MAY return creds unable to be used #517

Merged
merged 15 commits into from
Jul 12, 2018
6 changes: 6 additions & 0 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -1195,6 +1195,12 @@ utilize the Service Instance. Credentials SHOULD be unique whenever possible, so
access can be revoked for each binding without affecting consumers of other
bindings for the Service Instance.

This field MAY be omitted if the Service Broker either cannot return the credentials
or does not want to for security reasons. During an asynchronous bind
operation the Service Broker MUST include this field in at least the first response
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

first GET response (with link)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

link to what?

after the Service Binding has been successfully created, otherwise the Platform will
not have the credentials to pass along.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dug suggested

Note: some brokers (due to security concerns... blah blah) MAY choose to only return the credentials for a binding once even though there could be replayed binding requests or GETs of the binding resource.

#### Log Drain

There are a class of Service Offerings that provide aggregation, indexing, and
Expand Down