-
Notifications
You must be signed in to change notification settings - Fork 66
fix(cluster connect): display service account credentials #1237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -231,7 +231,7 @@ one = ''' | |
| Connection Details: | ||
|
|
||
| Service Type: {{.ServiceType}} | ||
| Service Name: {{.ServiceName}} | ||
| Service Name: {{.ServiceName}} | ||
| Kubernetes Namespace: {{.Namespace}} | ||
| Service Account Secret: {{.ServiceAccountSecretName}} | ||
| ''' | ||
|
|
@@ -288,7 +288,19 @@ one = 'Access token already exist on the specified namespace' | |
| one = 'Token Secret "{{.Name}}" created successfully' | ||
|
|
||
| [cluster.kubernetes.createSASecret.log.info.createSuccess] | ||
| one = 'Service Account Secret "{{.Name}}" created successfully' | ||
| one = ''' | ||
| Service Account Secret "{{.Name}}" created successfully | ||
|
|
||
| Client ID: {{.ClientID}} | ||
| Client Secret: {{.ClientSecret}} | ||
|
||
|
|
||
| Make a copy of the client ID and secret to store in a safe place. Credentials won't appear again after closing the terminal. | ||
|
|
||
| Execute the following command to grant access to the service-account using rhoas cli | ||
|
|
||
| rhoas kafka acl grant-access --producer --consumer --service-account {{.ClientID}} --topic "*" --group "*" | ||
|
||
|
|
||
| ''' | ||
|
|
||
| [cluster.kubernetes.createTokenSecret.log.info.createFailed] | ||
| one = 'Creation of the "{{.Name}}" secret failed:' | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should print the client secret for any reason. The CLI user only needs the client ID for ACL operations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though it may be irrelevant for cluster context, I think it will be useful if user needs a svc-account created like this for other purposes. wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's risky, it is printing a password that gives access to data. Default to safe, if people need it we can propose another solution. This is why the
service-accountcommands do not print anything and you must specify a file.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. Taking it down.