Bug 1476374 - [RFE] Regular ldap group sync by Openshift
[RFE] Regular ldap group sync by Openshift
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.5.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Paul Weil
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-28 13:59 EDT by jooho lee
Modified: 2017-07-31 12:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Comment 2 jooho lee 2017-07-31 12:21:31 EDT
//Delete client information
###############################################

1. Proposed title of this feature request:

*** Need a feature to sync ldap regularly by Openshift

4. Why does the customer need this? (List the business requirements here)

** There is no business requirement. 

5. How would the customer like to achieve this? (List the functional requirements here)

** Regularly synchronise ldap group by Openshift function 

6. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

** Regularly synchronise ldap group by Openshift function 

7. Is there already an existing RFE upstream or in Red Hat bugzilla?

** No

8. Does the customer have any specific time-line dependencies?

** no

9. Is the sales team involved in this request and do they have any additional input?

** No as far as i am aware of it.

10. List any affected packages

** Openshift container platform

11. Would the customer be able to assist in testing this functionality if implemented?

** I BELIEVE IT IS YES, BUT I CAN'T CONFIRM ON BEHALF OF CUSTOMER

###############################################

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