WildFly
  1. WildFly
  2. WFLY-705

Implement a User Agent and Remote Address Filter for the HTTP Management Interface

    Details

    • Similar Issues:
      Show 10 results 

      Description

      The HTTP Management interface provides access to manage the domain model, this interface is partly dependent on the protection supplied by an end users web browser.

      This feature request is to optionally filter inbound requests based on a configurable list of supported user agents and or remote addresses - this will mean buggy browser versions can be excluded and remote clients restricted.

      Anyone interested in contributing please feel free to ping darranl in #jboss-as7.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Andre Dietisheim added a comment -

            RFC 2616 states (http://www.ietf.org/rfc/rfc2616.txt, "14.43 User-Agent")

            User agents SHOULD include this field with requests.

            Thus imho not having a user-agent is perfectly valid, it's not mandatory to have it. Stuart merged my patch.

            Show
            Andre Dietisheim added a comment - RFC 2616 states ( http://www.ietf.org/rfc/rfc2616.txt , "14.43 User-Agent") User agents SHOULD include this field with requests. Thus imho not having a user-agent is perfectly valid, it's not mandatory to have it. Stuart merged my patch.
            Hide
            Brian Stansberry added a comment -

            I'm using the "Reject Pull Request" option not because the PRs were rejected (they were merged) but because they are undertow PRs and merging them there can't move this WildFly issue to a resolved state.

            If the updated undertow is in WildFly and that is enough to complete this task, please resolve this. Thanks!

            Show
            Brian Stansberry added a comment - I'm using the "Reject Pull Request" option not because the PRs were rejected (they were merged) but because they are undertow PRs and merging them there can't move this WildFly issue to a resolved state. If the updated undertow is in WildFly and that is enough to complete this task, please resolve this. Thanks!
            Hide
            Andre Dietisheim added a comment -

            Brian Stansberry if I read you right this issue covers only the untertow filters, the configuration options for the management service (HttpManagementResourceDefinition) will get implemented against WFLY-2635, right?

            Show
            Andre Dietisheim added a comment - Brian Stansberry if I read you right this issue covers only the untertow filters, the configuration options for the management service (HttpManagementResourceDefinition) will get implemented against WFLY-2635 , right?
            Hide
            Brian Stansberry added a comment -

            Andre Dietisheim Sounds fine. My last comment didn't mean that (it was just about details of the JIRA pull request workflow) but if there's a separate JIRA for config stuff, that's fine.

            Show
            Brian Stansberry added a comment - Andre Dietisheim Sounds fine. My last comment didn't mean that (it was just about details of the JIRA pull request workflow) but if there's a separate JIRA for config stuff, that's fine.
            Hide
            Darran Lofthouse added a comment -

            Yes following on from a few discussions we have had recently we need to expand quite a bit on the configuration of the management interfaces, this is one aspect, cross origin resource sharing is another, enhancements to security is another, there are a few others as well but essentially yes it all should happen under WFLY-2635.

            Show
            Darran Lofthouse added a comment - Yes following on from a few discussions we have had recently we need to expand quite a bit on the configuration of the management interfaces, this is one aspect, cross origin resource sharing is another, enhancements to security is another, there are a few others as well but essentially yes it all should happen under WFLY-2635 .

              People

              • Assignee:
                Andre Dietisheim
                Reporter:
                Darran Lofthouse
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development