Additional discussion of problems with enforcing Address checking

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • No Action
    • Affects Version/s: SAML 2.0 Profile PR
    • Component/s: Spec
    • None
    • Hide

      Consensus during 4/15 call was that the existing text mentions proxies and is sufficient to explain the problem.

      Show
      Consensus during 4/15 call was that the existing text mentions proxies and is sufficient to explain the problem.
    • Hide

      Consensus during 4/15 call was that the existing text mentions proxies and is sufficient to explain the problem.
      http://lists.oasis-open.org/archives/imi/201004/msg00018.html

      Show
      Consensus during 4/15 call was that the existing text mentions proxies and is sufficient to explain the problem. http://lists.oasis-open.org/archives/imi/201004/msg00018.html

      http://lists.oasis-open.org/archives/imi-comment/201004/msg00001.html

      Section 2.6.1 discusses the use of the Address attribute.
      "While moderately effective, this practice often proves impractical for services offered to large user populations, many of whom are likely to encounter proxies and network configurations that result in inability to satisfy the restriction"

      Just wanted to add as an observation that this is also impractical in situations where a selector relies on a cloud-based service for talking to the STS.
      E.g. the iPhone I-Card Selector works like that, therefore the IP address seen by the STS is always different from the IP of the selector.

            Assignee:
            Unassigned
            Reporter:
            Scott Cantor (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: