Bug 1305932 - No /login page for AEP registry oauth redirects
Summary: No /login page for AEP registry oauth redirects
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jordan Liggitt
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 15:48 UTC by Aaron Weitekamp
Modified: 2016-10-30 22:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-11 16:11:11 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Aaron Weitekamp 2016-02-09 15:48:43 UTC
Description of problem:
The Atomic Registry web UI is a cockpit-based service. If authentication is configured for HTPasswd, LDAP or Request Header providers the interface redirects to the oauth /login page. This is not served from AEP so it fails.

Version-Release number of selected component (if applicable):
# oc version
oc v3.1.1.6
kubernetes v1.1.0-origin-1107-g4c8e6f4

How reproducible:
always

Steps to Reproduce:
1. Configure AEP for HTPasswd, LDAP or Request Header identity provider
2. Run registry web UI as a pod via template
3. Launch registry web UI, try to login

Actual results:
Browser redirect fails

Expected results:
Browser should redirect to a login page where credentials are entered, then load registry web UI.

Additional info:

Comment 1 Jordan Liggitt 2016-02-09 16:23:51 UTC
Can you attach the config you are using?

Comment 2 Jordan Liggitt 2016-02-09 20:17:25 UTC
I can't recreate with htpasswd or LDAP. Request header auth doesn't use the login page, so it is not expected one would be registered.

Make sure you have "login: true" set in the config.

Comment 3 Jordan Liggitt 2016-02-11 16:11:11 UTC
closing as unrecreatable. please reopen with additional config/recreation steps if you still see it


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