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

Security Exceptions in Chrome/Firefox/Safari #48

Closed
scottcurtis2605 opened this issue Jul 23, 2018 · 8 comments
Closed

Security Exceptions in Chrome/Firefox/Safari #48

scottcurtis2605 opened this issue Jul 23, 2018 · 8 comments
Labels
duplicate This issue or pull request already exists

Comments

@scottcurtis2605
Copy link
Member

In the 'getting started' section, after navigating to the 'finish' directory and running the Maven command to start the server, the application metrics URL ('https://localhost:9443/metrics/application') causes a security exception in all three browsers. This does not occur with any of the other URLs in other guides.

While this is easy to bypass, it may be worth mentioning in the guide for less experienced users.

@evelinec
Copy link
Contributor

I thought there was such message in the guide before. @andrewdes can you take a look and fix.

@andrewdes
Copy link
Contributor

There will be a new function/fix for 18.0.0.3, so once that happens we will update the guide accordingly.

@evelinec
Copy link
Contributor

Assign to @justineechen to see to double check with 18003.

@justineechen
Copy link
Contributor

The security exception still occurs after 18003, this is the same security exception in Security Guide when users need to be authenticated.

@Joseph-Cass
Copy link

Joseph-Cass commented Apr 8, 2020

I'm running into this issue on Chrome, and the Visit this unsafe site option seems to have been removed in a Chrome update so I can't access the URL at all...

Your connection is not private
Attackers might be trying to steal your information from localhost (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_INVALID

It can still be bypassed on Safari and Firefox, for now, but my guess would be that they'll follow in the future.

@yeekangc
Copy link
Member

yeekangc commented Apr 8, 2020

Thanks, @Joseph-Cass. We will take a look.

@Joseph-Cass
Copy link

Thanks, @Joseph-Cass. We will take a look.

Thanks @yeekangc :) I have made a PR with one potential solution #102

@gkwan-ibm
Copy link
Member

close

@gkwan-ibm gkwan-ibm added the duplicate This issue or pull request already exists label Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

7 participants