We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue was migrated from Pagure Issue #2681. Originally filed by mharmsen (@mharmsen) on 2017-05-08 15:06:21:
In a default setup, both agent and ssl-ee are on the 8443 port .
It is understood that an agent needs client auth, but the ssl ee is requesting client auth too, even though client auth is not required.
If the request is ignored, access is still granted to ee pages, so it works ok, but it is confusing.
The text was updated successfully, but these errors were encountered:
Comment from mharmsen (@mharmsen) at 2017-05-08 15:07:08
Metadata Update from @mharmsen:
Sorry, something went wrong.
Comment from mharmsen (@mharmsen) at 2017-05-18 12:24:25
Comment from mharmsen (@mharmsen) at 2017-09-25 16:57:31
Comment from mharmsen (@mharmsen) at 2017-10-25 16:41:27
[20171025] - Offline Triage ==> 10.6
Comment from mharmsen (@mharmsen) at 2017-10-25 16:41:30
No branches or pull requests
This issue was migrated from Pagure Issue #2681. Originally filed by mharmsen (@mharmsen) on 2017-05-08 15:06:21:
In a default setup, both agent and ssl-ee are on the 8443 port .
It is understood that an agent needs client auth, but the ssl ee is requesting client auth too, even though client auth is not required.
If the request is ignored, access is still granted to ee pages, so it works ok, but it is confusing.
The text was updated successfully, but these errors were encountered: