Project

General

Profile

Bug #37726

Keep minio Secret Key after it is set in new UI

Added by Michael Reynolds about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Erin Clark
Category:
GUI (new)
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Services:S3 -> Configure
Set up the minio share
Enter the Secret Key and Confirm Secret Key
leave this section
return to S3 section
the Secret Key and Confirm Secret Key do not retain their previous entries

Once set, the Secret Key and Confirm Secret Key entries should be saved until changed

KeepMinioSecretKey-2018-07-16.png (45.1 KB) KeepMinioSecretKey-2018-07-16.png Michael Reynolds, 07/16/2018 08:53 AM
21540

Associated revisions

Revision 6e00ef35 (diff)
Added by Erin Clark about 2 years ago

Populate secret_key fields with secret_key data in s3 Ticket: #37726

History

#1 Updated by Dru Lavigne about 2 years ago

  • Assignee changed from Dru Lavigne to Erin Clark
  • Target version changed from Backlog to 11.2-BETA2

#2 Updated by Erin Clark about 2 years ago

  • Status changed from Unscreened to In Progress

#3 Updated by Dru Lavigne about 2 years ago

  • Subject changed from Keep minio Secret Key after it is set to Keep minio Secret Key after it is set in new UI
  • Status changed from In Progress to Ready for Testing
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#4 Updated by Michael Reynolds about 2 years ago

21540

Secret Key is now retained

#5 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF