ietf-wg-gnap / gnap-core-protocol

143 stars 26 forks source link

Rights and attributes SHOULD be equally supported #370

Closed Denisthemalice closed 2 years ago

Denisthemalice commented 2 years ago

The core draft defines

Privilege: right or attribute associated with a subject Access Token: a data artifact representing a set of rights and/or attributes

However, the core draft does not allow a RS to distinguish between rights and attributes.

The core protocol should define two fields in an access token request to distinguish between rights (i.e. capabilities) and attributes.

A set of standard attribute types should be defined to support ABAC (Attribute Based Access Control) : e.g. first name, family name, birth date, birth location, home address, email address, social security number, citizenship(s), etc …

fimbault commented 2 years ago

Closing as already answered several times