Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for claims specs #48

Merged
merged 2 commits into from Apr 15, 2019
Merged

Conversation

pelle
Copy link
Contributor

@pelle pelle commented Apr 13, 2019

We need a way to request various data about a claim. This allows us to specify most importantly an issuer, but also if the claim is required for signup.

A Claims Spec allows you to set specific requirements for the claims you are requesting.

Name Description Required
type The claims type yes
essential This claim is essential. A response should not be returned if user does not have this claim no
iss Array of DID's of allowed issuers of claims no
url URL for obtaining claim no
reason Short string explaining why you need this no

Examples:

{
  type: 'email',
  essential: true,
  iss: ['did:web:uport.claims'],
  url: 'https://uport.claims/email',
  reason: 'Whe need to be able to email you' 
}

@oed
Copy link
Contributor

oed commented Apr 14, 2019

Do you think something like this will be included in the DID-Auth spec?
cc @awoie

Copy link
Member

@simonas-notcat simonas-notcat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the iss field is an array, I think url should also be an array. Or something like this:

{
  type: 'email',
  essential: true,
  iss: [
    {
      did: 'did:web:uport.claims',
      url: 'https://uport.claims/email'
    },
    {
      did: 'did:web:sobol.io',
      url: 'https://sobol.io/verify'
    }
  ],
  reason: 'Whe need to be able to email you' 
}

@awoie
Copy link
Contributor

awoie commented Apr 15, 2019

@oed DID Auth is about exchanging a DID, while the Claims and Credentials people are talking about how to exchange credentials. But I assume that something like this will be included in the spec, yes.

@awoie
Copy link
Contributor

awoie commented Apr 15, 2019

It might be worth looking at the current claim manifest proposal and the way how they structure the request: https://hackmd.io/q-selsVyQQ-1p1LK7mHJxw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants