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
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
Currently the OSB API only supports basic auth. Adding an OAuth flow is being discussed, and so we should assume that long-term, there will be multiple forms of auth. Currently, we have a single field called AuthSecret in the BrokerSpec type, so the type of auth being used does not surface at all in the API. I think we should consider using a union type to make explicit in the broker spec what form of auth is requested. Example:
typeBrokerSpecstruct {
// other fields omittedAuthInfo*AuthInfo
}
typeAuthInfostruct {
BasicAuthSecret*v1.ObjectReference// in the future:OAuthSecret*v1.ObjectReference
}
...this would allow us to add new auth methods in a backward-compatible way.
Thoughts?
The text was updated successfully, but these errors were encountered:
This change will enable operators to chose different auth schemes for
brokers, as the OSB API spec begins to support more in the future.
Fixeskubernetes-retired#864
This change will enable operators to chose different auth schemes for
brokers, as the OSB API spec begins to support more in the future.
Fixeskubernetes-retired#864
arschles
added a commit
to arschles/kubernetes-service-catalog
that referenced
this issue
Jun 5, 2017
This change will enable operators to chose different auth schemes for
brokers, as the OSB API spec begins to support more in the future.
Fixeskubernetes-retired#864
arschles
added a commit
to arschles/kubernetes-service-catalog
that referenced
this issue
Jun 7, 2017
This change will enable operators to chose different auth schemes for
brokers, as the OSB API spec begins to support more in the future.
Fixeskubernetes-retired#864
* Converting the AuthSecret field to a union AuthInfo type
This change will enable operators to chose different auth schemes for
brokers, as the OSB API spec begins to support more in the future.
Fixes#864
* fixing test compile issues
* adding grammar to godoc
* adding grammar to open api description
Currently the OSB API only supports basic auth. Adding an OAuth flow is being discussed, and so we should assume that long-term, there will be multiple forms of auth. Currently, we have a single field called
AuthSecret
in theBrokerSpec
type, so the type of auth being used does not surface at all in the API. I think we should consider using a union type to make explicit in the broker spec what form of auth is requested. Example:...this would allow us to add new auth methods in a backward-compatible way.
Thoughts?
The text was updated successfully, but these errors were encountered: