Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9731

Login Module should log wrong property

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • EAP_EWP 5.2.0 ER6
    • EAP_EWP 5.2.0 ER1, EAP_EWP 5.2.0 ER4, EAP_EWP 5.2.0 ER5
    • Security
    • None
    • Not Required
    • NEW

    Description

      I have written test for JBPAPP-7794 and I found some errors. I don't get a WARN log in EAP 5.1.2 output if I use wrong property name, for example "WrongPropertyName", in login modules RoleMappingLoginModule and ClientLoginModule (it should write "Invalid or misspelled option: WrongPropertyName"). It happens because Login Modules (LdapLoginModule, LdapExtLoginModule, etc.) extends AbstractServerLoginModule (and there is this WARN logged) and RoleMappingLoginModule and ClientLoginModule implements LoginModule.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. SECURITY-704 Login modules should log invalid options.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-9823 LogWrongLoginModuleOptionsTest fails due to invalid reporting of correct options or failure to report wrong properties

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is incorporated by

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-10293 Upgrade to JBoss Negotiation 2.1.3

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBPAPP-9908 Upgrade JBoss security to 2.0.5.SP2

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBPAPP-7794 Login Modules Should Complain When Invalid Options Are Used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pskopek@redhat.com Peter Skopek
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: