Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Can no longer add multiple Authentication Decisions to the same hostname for different certificates

  • Không có trả lời
  • 1 gặp vấn đề này
  • 31 lượt xem
more options

For years we have been able to login to two different websites running on different ports on the same host with our Firefox browser (The last working version was 102.14.0-3.el7_9) our RHEL 7.x system. When I accessed the different sites, there was two Authentication Decisions, one sending one cert (We will call it CertA) to the system and the other listing sending a different cert (We will call that CertB) to the system, same hostname though.

I updated the Firefox browser to 115.7.0-1.el7_9 and ever since, when I navigate to the first website, it remembers the first Authentication Decision to send CertA to the system and works as intended. Then, I try to navigate to the second site and I never get prompted to pick a cert for the second site (CertB is what it should prompt for) and the connection attempt fails with a "Secure Connection Failed, Error code: SSL_ERROR_UNKNOWN_CA_ALERT" message.

If I go and delete the Authentication Decision for CertA, then go to the CertB site, I get prompted for the cert decision and I am able to login just fine. But, then if I try to go to the CertA site, I get the same error listed above.

I can use a band aid to check the "History > Always use private browsing mode" checkbox (Which never remembers the Auth. Decision) option in Firefox, then have to remember to close the browser each time I want to navigate from one site to the next. But I have never had to do that in the past and wondering if this is a new bug or if it is somehow considered a "Security Feature" or something.

I searched around the net a bit and couldn't find a way to manually add an Authentication Decision myself. Is that possible somehow with a config file edit on our Linux system somewhere?

Thanks kindly ahead of time for any consideration to my issue.

For years we have been able to login to two different websites running on different ports on the same host with our Firefox browser (The last working version was 102.14.0-3.el7_9) our RHEL 7.x system. When I accessed the different sites, there was two Authentication Decisions, one sending one cert (We will call it CertA) to the system and the other listing sending a different cert (We will call that CertB) to the system, same hostname though. I updated the Firefox browser to 115.7.0-1.el7_9 and ever since, when I navigate to the first website, it remembers the first Authentication Decision to send CertA to the system and works as intended. Then, I try to navigate to the second site and I never get prompted to pick a cert for the second site (CertB is what it should prompt for) and the connection attempt fails with a "Secure Connection Failed, Error code: SSL_ERROR_UNKNOWN_CA_ALERT" message. If I go and delete the Authentication Decision for CertA, then go to the CertB site, I get prompted for the cert decision and I am able to login just fine. But, then if I try to go to the CertA site, I get the same error listed above. I can use a band aid to check the "History > Always use private browsing mode" checkbox (Which never remembers the Auth. Decision) option in Firefox, then have to remember to close the browser each time I want to navigate from one site to the next. But I have never had to do that in the past and wondering if this is a new bug or if it is somehow considered a "Security Feature" or something. I searched around the net a bit and couldn't find a way to manually add an Authentication Decision myself. Is that possible somehow with a config file edit on our Linux system somewhere? Thanks kindly ahead of time for any consideration to my issue.

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.