Documentation ¶
Index ¶
Constants ¶
View Source
const JSONCredUsername = "_json"
JSONCredUsername is the username that we use for registry credentials to the Blimp registry to indicate that the password is a JSON-encoded auth.BlimpAuth, as opposed to a plain ID token.
Variables ¶
This section is empty.
Functions ¶
func GetAuth ¶
func GetAuth(req AuthenticatedRequest) *proto.BlimpAuth
func RegistryAuthHeader ¶
func RegistryAuthHeader(cred types.AuthConfig) (string, error)
Types ¶
type AuthenticatedRequest ¶
type BlimpRegistryAuth ¶
func BlimpRegcred ¶
func BlimpRegcred(auth *auth.BlimpAuth) (BlimpRegistryAuth, error)
func (BlimpRegistryAuth) ToBlimpAuth ¶
func (regAuth BlimpRegistryAuth) ToBlimpAuth() (*auth.BlimpAuth, error)
func (BlimpRegistryAuth) ToContainerRegistry ¶
func (regAuth BlimpRegistryAuth) ToContainerRegistry() authn.Authenticator
func (BlimpRegistryAuth) ToDocker ¶
func (regAuth BlimpRegistryAuth) ToDocker() types.AuthConfig
func (BlimpRegistryAuth) ToProtobuf ¶
func (regAuth BlimpRegistryAuth) ToProtobuf() *cluster.RegistryCredential
type RegistryCredentials ¶
type RegistryCredentials map[string]types.AuthConfig
func GetLocalRegistryCredentials ¶
func GetLocalRegistryCredentials(dockerConfig *configfile.ConfigFile) (RegistryCredentials, error)
GetLocalRegistryCredentials reads the user's registry credentials from their local machine.
func (RegistryCredentials) LookupByHost ¶
func (creds RegistryCredentials) LookupByHost(host string) (types.AuthConfig, bool)
func (RegistryCredentials) LookupByImage ¶
func (creds RegistryCredentials) LookupByImage(image string) (types.AuthConfig, bool)
func (RegistryCredentials) ToProtobuf ¶
func (creds RegistryCredentials) ToProtobuf() map[string]*cluster.RegistryCredential
type User ¶
type User struct {
Namespace string
}
func ParseIDToken ¶
Blimp used to use Auth0 for account management. Auth0 tokens were used to identify and authorize users. Blimp no longer does per-user authentication since only self-hosted clusters are supported. The "token" is used for namespacing resources, and access control to the cluster is controlled via a shared secret. Therefore, we don't do any validation on the token.
Click to show internal directories.
Click to hide internal directories.