stop the bogus http auth window from popping up, and causing confusion.
this is annoying, not a blocker. whenever you can get to it is fine.
I think I have fixed this. Can you test and confirm?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Needs Review)
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
Nov 05 11:06:22 <Evolution> nirik: oh, you fixed the windows thing? lemme check Nov 05 11:06:41 <nirik> Evolution: I hope so. :) Nov 05 11:09:37 <Evolution> nirik: still busted Nov 05 11:10:36 <nirik> Evolution: bummer, then I have 0 idea how to fix it... Nov 05 11:10:37 <Evolution> nirik: https://imgur.com/a/lwKKZLE
Metadata Update from @smooge: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
How about we ask the ipa folks if there's any better solution here than the one I tried? :)
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
@cheimes any ideas here? I tried the suggestion here:
https://jdshewey.blogspot.com/2017/08/fixing-annoying-popup-in-freeipa.html
ie, adding some stuff to ipa-redirect.conf.
That's bad advise. abompard and Arrfab were dealing with a broken FAS staging system because they applied the rules in https://pagure.io/fedora-infra/ansible/blob/master/f/roles/ipa/server/files/ipa-rewrite.conf#_24
It's an old bug in Windows that affects Chrome, Edge, and other browsers that use certain libraries from Windows. AFAIK Firefox is fine. You can read more in https://bugzilla.redhat.com/show_bug.cgi?id=1309041
The correct solution is https://github.com/gssapi/mod_auth_gssapi#example-1 . You might need a better browser match that just handles broken browsers on Windows.
Ah ha! good to know... will take a look, and many thanks!
It might also help if more people report the bug with Chrome Browser team and MSFT.
@jperrin Do you know anyone at Microsoft? :laughing:
Can you retest this now that we moved auth?
Please re-test and let us know if you still see this.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.