Bug 1327024

Summary: Kerberos authentication to console and API not fully functional(https://github.com/openshift/origin/pull/4566)
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: RFEAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED ERRATA QA Contact: weiwei jiang <wjiang>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: aos-bugs, charles_sheridan, erich, jliggitt, jmeyer, jokerman, jritenou, kabbott, marc.jadoul, mjs, mmccomas, tdawson, wsun
Target Milestone: ---Flags: jmeyer: needinfo+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1358399 (view as bug list) Environment:
Last Closed: 2016-09-27 09:37:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1358399    

Description Miheer Salunke 2016-04-14 06:29:21 UTC 
Description of problem:
We are trying to setup a configuration for supporting Active Directory authentication for Openshift using Kerberos.
The setup is documented in Openshift Enterprise 3.1 Installation and Configuration ยง 7.2.8 but is not fully working.

The part about login from a browser in the console seems working.
But when using the OC CLI, it seems this tool is not able to use kerberos authentication. It seems it is only able to authenticate through basic authentication.

Could you confirm OC CLI is kerberised?


Version-Release number of selected component (if applicable):
3.1.1

How reproducible:
Always

Steps to Reproduce:
1.Mentioned in the description
2.
3.

Actual results:
oc is not kerberised

Expected results:
it should be kerberised

Additional info:

Upstream fix https://github.com/openshift/origin/pull/4566
Comment 11 errata-xmlrpc 2016-09-27 09:37:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1933