• k8s-merge-robot's avatar
    Merge pull request #23574 from deads2k/add-extra · af71fa72
    k8s-merge-robot authored
    Automatic merge from submit-queue
    
    add user.Info.GetExtra
    
    I found myself wanting this field (or something like it), when trying to plumb the information about which scopes a particular token has.
    
    Only the token authenticators have that information and I don't want tokens to leak past the authenticator.  I thought about extending the `authenticator.Token` interface to include scopes (`[]string`), but that felt a little specific for what I wanted to do.  I came up with this as an alternative.
    
    It allows the token authenticator to fill in the information and authorizers already get handed the `user.Info`.  It means that implementors can choose to tie the layers together if they wish, using whatever data they think is best.  
    
    @kubernetes/kube-iam
    af71fa72
Name
Last commit
Last update
..
framework Loading commit data...
auth_test.go Loading commit data...
benchmark-controller.json Loading commit data...
client_test.go Loading commit data...
configmap_test.go Loading commit data...
doc.go Loading commit data...
dynamic_client_test.go Loading commit data...
etcd_tools_test.go Loading commit data...
extender_test.go Loading commit data...
kubectl_test.go Loading commit data...
master_benchmark_test.go Loading commit data...
master_test.go Loading commit data...
metrics_test.go Loading commit data...
openshift_test.go Loading commit data...
persistent_volumes_test.go Loading commit data...
pods.go Loading commit data...
quota_test.go Loading commit data...
scheduler_test.go Loading commit data...
secret_test.go Loading commit data...
service_account_test.go Loading commit data...
utils.go Loading commit data...