Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-1483 QE feedback
  3. RHDEVDOCS-1457

Please clarify CRW docs in User Management chapter

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • CRW 2.0.2
    • CRW 1.2.2
    • Dev Spaces
    • None
    • devex docs #175 Nov 6-Nov 26, devex docs #176 Nov 27-Dec 17, devex docs #177 Dec 18-Jan 7, devex docs #178 Jan 8-Jan 28, devex docs #179 Jan 29-Feb 18, devex docs #180 Feb 19-Mar 10
    • 8

      Please refine the "User Management" chapter (13):

      Doc says " If CodeReady Workspaces is deployed on OpenShift: Go to the OpenShift web console and navigate to the Keycloak namespace." -> not found on https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.0/html-single/administration_guide/index
      This isn't true. In a default installation, there is no namespace called 'keycloak', but there is a route in the CRW installation namespace.

      Section 13.7. 'Managing users' has a dead link to Keycloak doc.

      Section 13.8 references 'pre-configured MTP servers', should be 'SMTP' servers. -> not found on https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.0/html-single/administration_guide/index

      Section 13.9.3 reads "CodeReady Workspaces Swagger can be accessed from http://che_host:8080/swagger." It seems it is on the default port (not 8080). -> handled in https://issues.redhat.com/browse/RHDEVDOCS-1501

      Section 13.10.7. 'Super-privileged mode' does not explain how to use Super mode except through a che.env file (which is not available in scenarios like an OperatorHub installation). -> handled in https://issues.redhat.com/browse/RHDEVDOCS-1527

              ffloreth@redhat.com Fabrice Flore-Thébault
              rhn-support-rick Rick Wagner
              Kevin White, Shankaranarayanan Govindarajan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: