Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13141

Improvements to Elytron Client sections

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Minor
    • None
    • None
    • Documentation
    • 8

    Description

      The following feedback is pulled from JBEAP-7155 for post-GA work:

      ----------------------------------------------------------------------------------------
      Following should be currently improved in section 4.2. CONFIGURE CLIENT AUTHENTICATION WITH ELYTRON CLIENT:

      • Add some information which answers on following questions (it can be added before Table 4.1. Common Rules):
        • What happens if list of match-* is empty in rule - it will match or not?
        • If more match-* are set, it must match all of them or at least one of them to choose given rule?
      • Table 4.1. Common Rules should be improved
        • match-path - there is information that given /my/path/ matches on http://127.0.0.1:9990/my/path. There is missing information whether /my/path/ would also match on http://127.0.0.1:9990/my/path/subresource? Add this information also to table Table A.2. Match-* (match-rule-type) in APPENDIX A. REFERENCE MATERIAL.
        • match-purpose - add an example. Add this example also to table Table A.2. Match-* (match-rule-type) in APPENDIX A. REFERENCE MATERIAL.
      • Provide table with description of basic methods of AuthenticationConfiguration. Similar table as e.g. Table 4.2. Common Rules can be used for basic methods of AuthenticationConfiguration (e.g. useName, usePassword, useRealm, allowSaslMechanisms ...). It can be added at the end of section 4.2.2. The Programmatic Approach.

      What should be improved in APPENDIX A. REFERENCE MATERIAL:

      • Table A.4. authentication-configuration-type Attributes
        • "set-host", "set-port", "set-protocol", "set-mechanism-realm" description is not sufficient. What does it mean when some of these attributes are set?
        • provide example for "rewrite-user-name-regex"
      • Table A.5. key-store Attributes
        • "key-store-credential" need reformulation (the credential store contains password for accessing key store)
      • Table A.6 ssl-context
        • "cipher-suite" description is not sufficient. Which cipher suites are available? How can I set more cipher suites (+separators)?
          ----------------------------------------------------------------------------------------

      Also need to determine whether we should really even be documenting the XSD elements in the docs. See https://issues.jboss.org/browse/JBEAP-7155?focusedCommentId=13460183&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13460183 and other comments in JBEAP-7155 for the discussion.

      Attachments

        Issue Links

          Activity

            People

              dfitzmau@redhat.com Darragh Fitzmaurice
              rhn-support-ahoffer Andrea Hoffer
              Ondrej Lukas Ondrej Lukas (Inactive)
              Ondrej Lukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: