Ryan Richard 288d9c999e Use custom suffix in `Spec.Authenticator.APIGroup` of `TokenCredentialRequest` ... When the Pinniped server has been installed with the `api_group_suffix` option, for example using `mysuffix.com`, then clients who would like to submit a `TokenCredentialRequest` to the server should set the `Spec.Authenticator.APIGroup` field as `authentication.concierge.mysuffix.com`. This makes more sense from the client's point of view than using the default `authentication.concierge.pinniped.dev` because `authentication.concierge.mysuffix.com` is the name of the API group that they can observe their cluster and `authentication.concierge.pinniped.dev` does not exist as an API group on their cluster. This commit includes both the client and server-side changes to make this work, as well as integration test updates. Co-authored-by: Andrew Keesler <akeesler@vmware.com> Co-authored-by: Ryan Richard <richardry@vmware.com> Co-authored-by: Margo Crawford <margaretc@vmware.com>		2021-02-03 15:49:15 -08:00
..
testdata	Rename pinniped-server -> pinniped-concierge	2020-10-06 14:59:03 -04:00
server.go	Use custom suffix in `Spec.Authenticator.APIGroup` of `TokenCredentialRequest`	2021-02-03 15:49:15 -08:00
server_test.go	Avoid double registering types in server scheme	2021-02-03 12:16:57 -05:00