OAuth client instructions are ambiguous

[sarahmaddox]

From @vfontama on December 21, 2018 21:21

The instructions to create credentials is a bit ambiguous. Specifically, in step 2 where we set the "Authorized redirect URIs" the instructions have this sample: "https://.endpoints..cloud.goog/_gcp_gatekeeper/authenticate".

The is straightforward. However, the is confusing. It is not clear which name to use: In the screenshot the "Name" field has a different name from the name used in the "Authorized redirect URIs" field. So it's not clear if we should use the same name or not.

Copied from original issue: kubeflow/pipelines#586

[sarahmaddox]

From @yebrahim on December 21, 2018 21:23

/assign @jlewi
/assign @kunmingg
I thought this can be clearer as well, any thoughts guys?

[sarahmaddox]

From @kunmingg on December 21, 2018 23:6

docs located at: https://github.com/kubeflow/website/blob/master/content/docs/started/getting-started-gke.md

[sarahmaddox]

+1 that it's confusing. The "Name" in the UI is an arbitrary name that the user gives to this particular OAuth client ID. I'll clarify that in the docs.

/assign

[sarahmaddox]

/unassign @jlewi jlewi
/unassign @kunmingg

[jlewi]

Thanks @sarahmaddox is this fixed by #377?

[sarahmaddox]

Yes it is. I don't know why the "fixed" annotation on the PR didn't work.
/close

[k8s-ci-robot]

@sarahmaddox: Closing this issue.

In response to this:

Yes it is. I don't know why the "fixed" annotation on the PR didn't work.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.