Skip to content

Releases: inrupt/solid-client-access-grants-js

v2.1.2

06 Feb 16:21
57f0502
Compare
Choose a tag to compare

Bugfixes

  • The JSON-LD/JSON normalization is now applied not only when issuing an Access Request
    or an Access Grant, but also when dereferencing one.

  • JSON-LD/JSON alignment: We are processing Verifiable Credentials as plain JSON,
    while they actually are JSON-LD. This creates some discrepancies:

    • The Access Grants and Access Requests status is now accepted in its abbreviated
      form, and not only as a fully qualified IRI, as allowed by the JSON-LD context.
    • Arrays containing a single value are also accepted as a literal equal to said
      single value.

    This is a stopgap solution: a proper fix would be to do full JSON-LD parsing,
    but we aren't doing it for the moment because of issues between existing libraries
    and our build setup.

v2.1.0

09 Jan 13:15
814b4f4
Compare
Choose a tag to compare

New Features

  • Added the createContainerInContainer method.
  • Added saveSolidDatasetInContainer method.
  • Added the updateAcr flag to the options that can be included when calling
    the approveAccessRequest method. updateAcr will default to true. Note that
    this is an advanced feature, and only users having a good understanding of the
    relationship between Access Grants and ACRs should deviate from the default.
    Additional information is available in the ESS documentation
  • Added the inherit flag to issueAccessRequest and approveAccessRequest to
    allow controlling whether the issued Access Grant should apply recursively to
    the target containers' contained resources.
  • The getAccessGrantAll method now allows discovering recursive Access Grants
    issued for an ancestor container.

Minor changes

  • The getters module contains functions and a class to interact with Verifiable
    Credentials without having to hard-code the data model in your application.

v2.0.0

03 Nov 10:47
2d23b3b
Compare
Choose a tag to compare

Breaking change

  • getAccessRequestFromRedirectUrl and getAccessGrantFromRedirectUrl no longer
    pick up VC passed by value, and only support passing by IRI. This is for security
    reasons, as passing a VC by value in the IRI leaks information. This removes a
    behavior that has been deprecated in v0.5.0. This change doesn't affect you if
    you are using the query parameters accessors (getAccessRequestFromRedirectUrl
    and getAccessGrantFromRedirectUrl).

New features

  • getAccessRequestFromRedirectUrl and getAccessGrantFromRedirectUrl now accept URL
    objects as well as plain strings.
  • approveAccessRequest now accepts a null expiration date override, resulting
    in the expiration date from the Access Request not being applied to the Access Grant.

This release also includes dependencies update.

v1.1.0

02 Sep 17:27
e6dfae2
Compare
Choose a tag to compare

New Features

  • Added resource APIs for overwriteFile and saveFileInContainer, these
    compliment the existing getFile method.

Other Changes

  • Refactored resource APIs (getFile, getSolidDataset, saveSolidDatasetAt)
    and added end-to-end test coverage of these APIs.
  • Improved jest setup for node & browser unit tests.
  • Added a more extensive demo app.

Pull Requests

New Contributors

Full Changelog: v1.0.2...v1.1.0

v1.0.2

22 Jun 08:25
daa6d5e
Compare
Choose a tag to compare

New features

  • approveAccessRequest, getAccessGrant, getAccessGrantFromRedirectUrl now accurately return an AccessGrant.
  • getAccessRequestFromRedirectUrl now accurately return an AccessRequest.

Bugfix

  • Fix Node 14 atob/btoa compatibility issue.

v1.0.1

06 Jun 20:23
caa7e91
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.0...v1.0.1

v1.0.0

06 Jun 18:30
264da10
Compare
Choose a tag to compare

No changes from 0.6.1 - finalizing interface for 1.0.0 release.

v0.6.1

06 Jun 12:10
dca3867
Compare
Choose a tag to compare

Bugfix

  • Export all types via Rollup.
  • Fix demo application.

Breaking change

  • Drop Node 12 support.

v0.6.0

06 Apr 11:52
d7eb4a6
Compare
Choose a tag to compare

New features

  • getAccessGrantAll supports a new option, includeExpired. By default,
    only grants that are still valid are returned by the VC provider. If set to true,
    grants that have expired will also be included in the response.
  • issueAccessRequest now generates an access request VC including the resource
    owner in the hasConsent field with the isConsentForDataSubject predicate. This
    will enable resource owners to dereference access requests IRIs to their resources.

Bugfix

  • When type-checking an Access Grant (e.g. using getAccessGrant), only accepted
    Grants were supported. Support for denied Grant has now been added.
  • When using an Access Grant to get an Access Token, one of the claims from the
    server response was unaligned with the spec. This inconsistency has been fixed on
    the server-side with backwards-compatibility, and now on the client side too. This
    change is transparent to users.
  • approveAccessRequest wasn't using the default session from @inrupt/solid-client-authn-browser
    to set the ACR access appropriately, resulting in 401 Unauthenticated errors.
  • getAccessRequestFromRedirectUrl was deserializing the received VC expecting
    an URL-encoded value, instead of a base64-encoded value, which is how it is serialized
    when redirecting the user to the VC management app.