Bug 1261912

Summary: [RFE] Enable AD/ADFS support in RGW
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vimal Kumar <vikumar>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: shylesh <shmohan>
Severity: medium Docs Contact: Bara Ancincova <bancinco>
Priority: medium    
Version: 1.3.0CC: cbodley, ceph-eng-bugs, hnallurv, icolle, kbader, kdreyer, mbenjamin, mwatts, nlevine, owasserm, rnalakka, sweil, tvvcox, vumrao, yweinste
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 2.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.0-1.el7cp Doc Type: Enhancement
Doc Text:
Documented with BZ#1261891
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:26:21 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: 1322504    

Comment 2 Neil Levine 2015-09-22 18:47:07 UTC
*** Bug 1244737 has been marked as a duplicate of this bug. ***

Comment 6 Marcus Watts 2016-03-14 22:21:01 UTC
STS is NOT in master or v10.0.3.  And not in the "jewel" branch by March 9th.  The current plan is to target kraken & backport to jewel.

Comment 7 Neil Levine 2016-03-14 23:03:48 UTC
Ths card refers to the native AD support, not STS.

STS is covered under https://bugzilla.redhat.com/show_bug.cgi?id=1274084

Comment 8 Ken Dreyer (Red Hat) 2016-04-26 20:44:38 UTC
Matt, is this feature complete in v10.2.0?

Comment 9 Ken Dreyer (Red Hat) 2016-05-10 20:32:30 UTC
This is AD LDAP support, not STS.

From the call today: It is in v10.2.0

Comment 15 shylesh 2016-08-04 15:36:49 UTC
Verified with AD on Windows 2012. All the targeted tests are complete hence marking this as verified.

Special thanks to Matt for providing his AD setup for testing.

Comment 17 errata-xmlrpc 2016-08-23 19:26:21 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:1755