Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-399

More flexible PeerIdentity concept

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 1.1.0.Beta4
    • None
    • API / SPI
    • None
    • Medium

      The existing PeerIdentity APIs aren't working out, because the separation of the PeerIdentity and its backing implementation introduces too much complexity while making it too difficult for service providers to do anything with them.

      Simplify the API so that PeerIdentity and PeerIdentityContext are (secure) abstract classes which can be extended by providers, which can then use the API directly in a more useful manner. Move responsibility for managing anonymous identities on to the subclass, with the new default being "no identity in particular", which allows e.g. the Remoting provider to default to the connection identity, while other providers can default to the anonymous identity (if there is one).

              dlloyd@redhat.com David Lloyd
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: