atlas_rb 1.15.0 → 1.15.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8a32e3df39d1a5f9648e47a42b88be5deff1b28dc696f9575a073baac4b9fa58
-  data.tar.gz: cb224b216444752165a39f242120e478cbe03c4a2613e36b19665d1897ec59b8
+  metadata.gz: 7c13a532b6294a91f70d7741ddda78b489f0b0ef9125f9276cd10618ad1119cd
+  data.tar.gz: cff5b9e17d774c251b986baea4507afb497c5b744f7d985e20f4f1e1cd6c5396
 SHA512:
-  metadata.gz: 43cf01a77168ae4ae78de02bf26403e9c116b63f18d685adc7bf82275124aaa498129ea1a8dad9c4867330b455c236f68f20b05763743be8b4db97ceef0b8324
-  data.tar.gz: 6fb09278babb33a465f090e32b0616649bddd4fb043337cbeace8c6c0b7f83ff0cde6710f01eecec69e91d8c65db2d58c67683a7c55496078f090312d7f77317
+  metadata.gz: 92b30a85e8b1870693c3ec5df6e5b33faf285de1c4b05df4dac7f6c124be1250cfbb5f6bbb066de3fdb01c70420b376b46eb265a2dd8104b1198f4d326c958a3
+  data.tar.gz: 3cf3ae964a6c47e958bf6ca294a9b672ba0dcf5eede7f645c3ea7498fb264c2ad5b6e42e6ee96519e4360fccb280d02d485db9d92df64c07b8aa59a3d5760e63

data/.version

@@ -1 +1 @@
-1.15.0
+1.15.1

data/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## 1.15.1
+
+### Fixed — `Resource.permissions` no longer coerces a refused read to `nil`
+
+Atlas gates `GET /resources/:id/permissions` on the caller's read right over
+the resource itself, because the envelope names the Grouper groups and the
+depositor's NUID. A caller who may not read the resource gets a real `403`
+carrying `{ "error", "action", "subject" }`.
+
+The binding parsed that body without consulting the status. The error envelope
+has no `"resource"` key, so `JSON.parse(body)["resource"]` returned the same
+`nil` an unknown id returns — the status, the message and the distinction were
+all gone before the caller saw anything. A host reading this to drive its own
+gate rendered "not found" for a resource the reader was merely not allowed to
+see.
+
+`permissions` now routes through `fetch_resource`, the guarded read path every
+typed `find` already uses:
+
+| Atlas answers | `permissions` |
+|---|---|
+| `200` | the ACL `Mash` |
+| `404` | `nil` — unchanged |
+| `403` | raises `AtlasRb::ResourceError`, `status == 403` |
+
+A host that wants the old "nil for anything unreadable" behaviour rescues
+`AtlasRb::ResourceError` and returns `nil` itself.
+
+The YARD example was also wrong: the envelope carries `type`, `depositor`,
+`proxy_uploader`, `edit_users`, `read`, `edit` and `embargo`, never `id`.
+
 ## 1.15.0
 
 ### Changed — the transport reuses connections instead of opening one per request

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    atlas_rb (1.15.0)
+    atlas_rb (1.15.1)
       faraday (~> 2.7)
       faraday-follow_redirects (~> 0.3.0)
       faraday-multipart (~> 1)

data/lib/atlas_rb/resource.rb

@@ -159,6 +159,13 @@ module AtlasRb
 
     # Fetch the access-control entries for a resource.
     #
+    # Routed through {fetch_resource} so a refusal stays a refusal. Atlas gates
+    # this endpoint on the caller's read right over the resource itself and
+    # answers `403` with an `{ "error", "action", "subject" }` envelope, which
+    # has no `"resource"` key — parsing it directly would hand back the same
+    # `nil` an unknown id gives, and a caller cannot tell "may not see it" from
+    # "is not there".
+    #
     # @param id [String] an Atlas resource ID.
     # @param nuid [String, nil] optional acting user's NUID. On the relay-signing
     #   path it is signed into the assertion `sub`; on the BYO-JWT (`ATLAS_JWT`)
@@ -166,17 +173,21 @@ module AtlasRb
     # @param on_behalf_of [String, nil] optional NUID for the `On-Behalf-Of`
     #   header. Falls through to {AtlasRb.config}.default_on_behalf_of when
     #   omitted.
-    # @return [Hash] the `"resource"` payload from `GET /resources/<id>/permissions`,
-    #   typically containing read/write/admin grant lists.
+    # @return [AtlasRb::Mash, nil] the `"resource"` payload from
+    #   `GET /resources/<id>/permissions`, typically containing read/write/admin
+    #   grant lists; `nil` when Atlas reports the resource is absent (`404`).
+    # @raise [AtlasRb::ResourceError] on any other non-2xx — notably `403`,
+    #   carrying `status` so the caller can render its own forbidden page.
     #
     # @example
     #   AtlasRb::Resource.permissions("abc123")
-    #   # => { "id" => "abc123", "read" => [...], "write" => [...] }
+    #   # => { "type" => "Work", "depositor" => "001234567",
+    #   #      "read" => [...], "edit" => [...], "edit_users" => [...] }
     def self.permissions(id, nuid: nil, on_behalf_of: nil)
-      AtlasRb::Mash.new(JSON.parse(
-        connection({}, nuid, on_behalf_of: on_behalf_of)
-          .get('/resources/' + id + '/permissions')&.body
-      ))["resource"]
+      result = fetch_resource('/resources/' + id + '/permissions', nuid: nuid, on_behalf_of: on_behalf_of)
+      return nil if result.nil?
+
+      AtlasRb::Mash.new(result)["resource"]
     end
 
     # Fetch the audit-event history for a resource.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: atlas_rb
 version: !ruby/object:Gem::Version
-  version: 1.15.0
+  version: 1.15.1
 platform: ruby
 authors:
 - David Cliff
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-09-02 00:00:00.000000000 Z
+date: 2026-09-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday