Uploaded image for project: 'Spring Security'
  1. Spring Security
  2. SEC-1335

Use up-to-date attribute type names in the OpenID sample

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Component/s: Samples
    • Labels:
      None

      Description

      The OpenId example currently uses "http://schema.openid.net/contact/email" and "http://schema.openid.net/namePerson/friendly" as "attribute exchange" attribute types in the wiring file. The "http://schema.openid.net" attribute schema is now out-dated, and "http://axschema.org/" should be used in its place; see http://www.axschema.org/ for details.

      It is worth noting that http://openid.net/specs/openid-attribute-exchange-1_0.html uses "AX" names and references "http://www.axschema.org/" as the preferred schema. FWIW, Google supports both the old and new schemas, but Yahoo only supports the new one. I haven't tried other providers.

        Activity

        crawley Stephen Crawley created issue -
        Hide
        luke Luke Taylor added a comment -

        myopenid (which we use for testing) doesn't appear to support the axschema attributes, so I'm not going to change this at the moment.

        Developers should be aware of what their provider supports and use the appropriate schemas and attribute names to put in their configuration.

        Show
        luke Luke Taylor added a comment - myopenid (which we use for testing) doesn't appear to support the axschema attributes, so I'm not going to change this at the moment. Developers should be aware of what their provider supports and use the appropriate schemas and attribute names to put in their configuration.
        luke Luke Taylor made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 3.0.0 [ 11380 ]
        Assignee Luke Taylor [ luke ]
        Resolution Won't Fix [ 2 ]
        luke Luke Taylor made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        tmarshall Trevor Marshall made changes -
        Workflow jira [ 29616 ] SPR Workflow [ 55025 ]
        Hide
        issuemaster Spring Issuemaster added a comment -
        Show
        issuemaster Spring Issuemaster added a comment - This issue has been migrated to https://github.com/spring-projects/spring-security/issues/1582
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        18h 18m 1 Luke Taylor 18/Dec/09 5:03 AM
        Resolved Resolved Closed Closed
        426d 5h 37m 1 Luke Taylor 17/Feb/11 10:40 AM

        This list may be incomplete, as errors occurred whilst retrieving source from linked applications:

        • Request to http://cr:8080/ failed: Error in remote call to 'cr' (https://cr.projectreactor.io) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={expand=changesets[0:20].revisions[0:29],reviews, query=SEC-1335}, methodType=GET}] : javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

          People

          • Assignee:
            luke Luke Taylor
            Reporter:
            crawley Stephen Crawley
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development