Bug 1817647 - Migration UI Login redirect not working when using custom CA in the default ingress router
Summary: Migration UI Login redirect not working when using custom CA in the default i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 1.4.z
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-26 17:47 UTC by Erik Nelson
Modified: 2021-04-07 21:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 21:08:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Erik Nelson 2020-03-26 17:47:04 UTC
Taken from a UI issue in github, I want to make sure this is reproduced and added to QE tests: https://github.com/konveyor/mig-ui/issues/755

---

After adding a custom self-signed defaultcertificate following in the default ingress router

The web UI fails to login with the follwoing error:

{"error":"invalid_request","error_description":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."}

The oauth server pods shows this message in the log:

    http: TLS handshake error from <ingress_pod_ip>:43440 : remote error: tls: unknown certificate

It seems that the web UI is not using the bundle from /etc/ssl/certs to validate the certificate against the ingress router

Comment 2 Erik Nelson 2021-04-07 21:08:09 UTC
Closed as stale, please re-open if the issue persists.


Note You need to log in before you can comment on or make changes to this bug.