Skip to content
New issue

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

web admin: issues with HTTP SSL certificates #5042

Closed
nqb opened this issue Jan 9, 2020 · 5 comments
Closed

web admin: issues with HTTP SSL certificates #5042

nqb opened this issue Jan 9, 2020 · 5 comments

Comments

@nqb
Copy link
Contributor

nqb commented Jan 9, 2020

I have two issues with HTTP SSL certificates configuration:

  1. If I edit configuration of my HTTP certificate, I didn't see a text area called "Certificate Authority" like for RADIUS certificate. However, there is a button "Choose Certificate Authority". If I upload my root certificate with this button and make another change in the form, the Certificate Authority text area appeared.

  2. When I try to add intermediate CA certificates using upload or copy/paste in text area, my intermediate CA certificate doesn't appear. If I save my changes, I got following error : "Failed to parse one of the certificate CAs"

To Reproduce
Steps to reproduce the behavior:

  1. Try to upload a CA certificate for HTTP
  2. Try to add/upload an intermediate certificate for HTTP

Expected behavior

  • Text area for Certificate Authority in HTTP section
  • Intermediate certificate(s) correctly handle
@nqb nqb added this to the PacketFence-9.3 milestone Jan 9, 2020
@nqb nqb assigned cgx Jan 9, 2020
@cgx cgx closed this as completed in 0ace980 Jan 10, 2020
@nqb nqb reopened this Jan 13, 2020
@nqb
Copy link
Contributor Author

nqb commented Jan 13, 2020

Hello @cgx,

It looks like you fixed 2. with 0ace980.

However, 1. is still presents and now "Choose Certificate Authority" button is missing for HTTP certificate.

@nqb
Copy link
Contributor Author

nqb commented Jan 13, 2020

I will update milestone because this issue affects 9.2 and need to be cherry-picked in maintenance.

@nqb
Copy link
Contributor Author

nqb commented Jan 13, 2020

Now I'm confused because I found this issue: #4353.

I will speak with @julsemaan about this topic.

@nqb
Copy link
Contributor Author

nqb commented Jan 13, 2020

Closing because we don't need to provide a CA certificate for HTTP: end-devices will use CAs in their certificate stores to validate server certificate.

@nqb nqb closed this as completed Jan 13, 2020
@nqb
Copy link
Contributor Author

nqb commented Jan 13, 2020

Not possible to backport this change in maintenance/9.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants