-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
RFE: fully support/enable htpasswd idp (beyond single admin)
-
False
-
False
-
To Do
-
XCMSTRAT-1005 - M2: htpasswd expanded UI
-
80% To Do, 0% In Progress, 20% Done
-
(9/18) old UX, need to re-familiarize, review
User Story
As a OSD or ROSA cluster administrator, I'd like to utilize htpasswd as an IDP, just as well as it can be in OCP. I'd like to plug in the yaml config for the htpasswd oauth provider through the OCM UI and it should populate in my cluster to enable htpasswd.
This should allow me to map more than just the single admin user as its implemented currently.
For each product, documentation will need to be added for this IDP.
For this feature, OCM UI will need to be updated to accomodate.
Acceptance Criteria
- All the things that have to be done for the feature to be ready to
release.
Default Done Criteria
- All existing/affected SOPs have been updated.
- New SOPs have been written.
- Internal training has been developed and delivered.
- The feature has both unit and end to end tests passing in all test
pipelines and through upgrades. - If the feature requires QE involvement, QE has signed off.
- The feature exposes metrics necessary to manage it (VALET/RED).
- The feature has had a security review.* Contract impact assessment.
- Service Definition is updated if needed.* Documentation is complete.
- Product Manager signed off on staging/beta implementation.
Dates
Integration Testing:
Beta:
GA:
Current Status
GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.
References
Links to Gdocs, github, and any other relevant information about this epic.