Skip to content
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

Admin launcher does not persist or store previously accepted certificates for client plugins #4275

Open
rbeckman-nextgen opened this issue May 11, 2020 · 1 comment

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

The Launcher does not persist approvals for certificates. Traditional JavaWS has the option to permanently trust the certificate so should the Launcher.

Repro steps:

  1. Start the Launcher
  2. Launch an MC instance which has a self-signed client library
  3. Get the yes/no prompt to accept the certificate
  4. Quit MC
  5. Quit the Launcher
  6. Repeat steps 1 and 2
  7. You'll be prompted again

Imported Issue. Original Details:
Jira Issue Key: MIRTH-4399
Reporter: jbartels
Created: 2019-03-28T11:11:46.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the Future Planned milestone May 11, 2020
@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Fixing this issue may be a workaround for MIRTH-4367 in that if the certificate acceptance persists a user would only run into the dialog once and thus reduce their exposure to the crashing behavior when that dialog is shown.

Imported Comment. Original Details:
Author: jbartels
Created: 2019-03-28T11:13:12.000-0700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.