Closed deepakpal-in closed 9 months ago
Hi @deepakpal-in, In your browser, did you trust your self-signed certificate? Which browser, version, OS platform do you use?
I have added/installed certs in the trusted root certificate authority. Still same results. Not able to run the service getting 404 error along with that. It's still showing certificate related error.
Browser: Edge 88, Chrome 107 OS: Windows server 2022 / Windows 10 Pro / Windows Server 2019
@aabouzaid Is this is any solution available for this issue ? Looking forward to solve this problem and try using the camunbda 8 platform.
@deepakpal-in I plan to debug it next week. But if you want a quick solution, I believe by setting set Identity context to the root of the domain, that should work.
So you will have the following:
Describe the bug:
Not able to run identity completely on https using the subpath:
Actual behavior:
Identity is giving Status Code: 404 after login for below files:
https://myELB.us-east-1.elb.amazonaws.com/static/js/main.97750144.js https://myELB.us-east-1.elb.amazonaws.com/static/css/main.42f6e202.css
then for https://myELB.us-east-1.elb.amazonaws.com//**identity**/serviceWorker.js?basePath=%2Fidentity it is giving 200
but again for https://myELB.us-east-1.elb.amazonaws.com//favicon.png it is ginvign Erroe 404.
Expected behavior:
Identity should work normally with self signed certificate warning in the browser.
How to reproduce:
Below is my custom value file:
Logs:
Logs from my keycloak pod:
Environment: