Red Hat Bugzilla – Bug 1308455
Couldn't list the project on web console using Edge25
Last modified: 2016-05-23 11:09:46 EDT
Created attachment 1127202 [details]
Description of problem:
When use Edge25 to access V3 STG web console, couldn't list user projects, neither could do operations.Other browsers work well(Firefox43,Chrome47,Safari9,IE11)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Login V3 STG through web console using Edge browser
1. After login, couldn't list user project, get "Access is denied" error, see attachment.
1. User project should be listed after login, and could do operations on web console
Created attachment 1127203 [details]
I see a certificate error in the top of the browser... has the certificate been trusted?
No, certificate was not trusted, i didn't see an option to add a website (URL) to a Trusted Zone in MS Edge.
will this certificate issue affect listing and other features? I didn't trust the certificate either on Chrome but everything in Chrome works fine.
When I login via CLI using token got from LocalStorage, I could list projects and do operations normally.
is there any possibility this is my network issue?
Determined looking at another bug that I think the cert issues with these servers have already been resolved. I'm fairly certain they had the OOTB self-signed certs at the time this was reported and are now using the right certs. This issue should be resolved.
Dev Preview Online is not accessible now, will verify when it's available
Created attachment 1140206 [details]
Also attach Edge 25 settings on my machine
Created attachment 1140207 [details]
I think there may be some misconfiguration on my Edge25
Just updating that I was able to reproduce the issue today, we are looking into it.
Just waiting for OPs to apply the workaround for the devpreview cluster.
workaround is applied to devpreview cluster, IE11 and Edge 25 are working now
Yes, IE 11 and Edge 25 could list projects on dev-preview-int iteration #3 now
*** Bug 1323204 has been marked as a duplicate of this bug. ***