Skip to content

Public trust/discovery services #11

@cyberphone

Description

@cyberphone

A generic problem with evolving ecosystems is maintaining interoperability without "freezing" specifications for extended periods of time.

Although my line of work is in payments, it is quite possible that identity/claims-consuming RPs also could benefit from being able to declare their capabilities and demands before the actual "transaction" takes place. This arrangement enables assertion producers to adapt assertions to the actual need of each RP. To make it scale, RPs would deploy .well-known URLs to trust/discovery services.

A somewhat dated but still relevant document:
https://cyberphone.github.io/doc/defensive-publications/authority-objects.pdf

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions