-
Bug
-
Resolution: Done
-
Normal
-
None
-
rhel-8.6.0
-
None
-
Low
-
OtherQA
-
4
-
rhel-sst-display-productivity
-
ssg_display
-
5
-
False
-
-
None
-
DESKTOP Cycle #3 10.beta phase, DESKTOP Cycle #4 10.beta phase, DESKTOP Cycle #5 10.beta phase, DESKTOP Cycle #2 10.0 phase
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem: WebRTC web-based applications do not start in FIPS mode.
Version-Release number of selected component (if applicable):
102.4.0-1.el8_6.x86_64
How reproducible: 100%
Steps to Reproduce:
1. Configure the machine for FIPS mode.
2a. Attempt to load Google Meet will result in "Couldn't start the video call because of an error"
2b. Attempt to load WebEx will result in "Connecting to audio...", no video.
2c. Attempt to load BitWarden will result in "An error has occurred. The operation failed for an operation-specific reason"
3. Perform the same procedure with Firefox ESR from Mozilla. Everything works as expected.
4. Perform the same procedure with Google Chrome. Everything works as expected.
5. Disable FIPS mode. Everything works as expected in Firefox.
6. the Simple RTCPeerConnection Video Test (https://mozilla.github.io/webrtc-landing/pc_test.html) also fails in FIPS mode.
Additional info:
