• False
    • Hide

      None

      Show
      None
    • False
    • Yellow
    • XCMSTRAT-32Automation / API
    • 29% To Do, 0% In Progress, 71% Done
    • Hide

      August 17 update

      • still pending Terraform and UI/HAC efforts

      OCM team update 10 Aug

      • Changes to be fully supported in ROSA release 1.2.25 (16th of August)
        • No change, enabling multiple users and day one cluster admin to be part of 1.2.25
        • Release pushed a week due to blockers not associated with this change

      Docs 20-July update
      OSDOCS-3348 open but on hold

      July 13, 2023 update
      There are still OCM, HAC and OSDOCS cards in the child epics to address.

      Show
      August 17 update still pending Terraform and UI/HAC efforts OCM team update 10 Aug Changes to be fully supported in ROSA release 1.2.25 (16th of August) No change, enabling multiple users and day one cluster admin to be part of 1.2.25 Release pushed a week due to blockers not associated with this change Docs 20-July update OSDOCS-3348 open but on hold July 13, 2023 update There are still OCM, HAC and OSDOCS cards in the child epics to address.
    • Yes
    • 0

      User Story

      As a customer of ROSA/OSD, I use the htpasswd idp for adding several users at once, sometimes across several interactions.
      I need to be able to both interactively and non-interactively add more than one user to the htpasswd idp.

      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.

      This feature also needs to be enabled & supported with our ROSA Terraform content.

      -------------------

      We should offer this through accepting a file (yaml file? htpasswd generated file?) and as CLI options perhaps like this...

       

      rosa create idp --type=htpasswd -c cluster --fromfile=myhtpassfile
      rosa create idp --type=htpasswd -c cluster --user=adejong,password1 --user tavni,password2 --user=byron,password3
      rosa edit idp --type=htpasswd -c cluster --user=adejong,password1 --user tavni,password2 --user=byron,password3
      

       

      This must work both interactively and non-interactively. This involves allowing full CRUD (create read update delete) of htpasswd idp users.

      This cannot break existing htpasswd or create-admin functionality.

       

      Acceptance Criteria

      1. users can create the htpasswd IDP by passing in a htpasswd file
      2. users can create the htpasswd IDP by passing in an array of users and password

            rh-ee-adejong Aaren de Jong
            rh-ee-adejong Aaren de Jong
            Unassigned Unassigned
            Brandi Munilla Brandi Munilla
            Aaren de Jong Aaren de Jong
            David Taylor David Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: