@toa.io/extensions.exposition 1.0.0-alpha.254 → 1.0.0-alpha.257

package/components/identity.roles/receivers/identity.federation.principal.js

@@ -0,0 +1,6 @@
+'use strict'
+
+/**
+ * @param {{ identity: string }} payload
+ */
+exports.request = (payload) => ({ input: { id: payload.identity } })

package/{components/context.toa.yaml → context.toa.yaml}

@@ -1,7 +1,6 @@
 # used for development only
 
 name: exposition
-packages: '*'
 registry: localhost
 
 amqp: amqp://localhost

package/documentation/credentials.md

@@ -57,12 +57,15 @@ constraints, and principal configuration.
 
 ## Federated credentials
 
-- `POST /identity/federation/:identity/` associates credentials from a trusted issuer.
+- `POST /identity/federation/:identity/` associates credentials from a trusted issuer and returns
+  the associated credential as it is listed.
 - `GET /identity/federation/:identity/` lists federated credentials.
 - `DELETE /identity/federation/:identity/:credential/` removes one federated credential.
 
+If the credentials are already associated with the Identity, the existing credential is returned.
+
 An Identity can have credentials from multiple issuers and can have multiple subjects from the
-same issuer. The `:credential` segment is the `id` returned by either listing resource. Federation
+same issuer. The `:credential` segment is the `id` returned by any of these resources. Federation
 resources are provider-independent; issuer-specific authorization flows remain the responsibility
 of the application.
 

package/features/identity.basic.feature

@@ -474,3 +474,57 @@ Feature: Basic authentication
 
       code: EXISTS
       """
+
+  Scenario: Adding basic credentials after they have been deleted
+    Given transient identity
+    When the following request is received:
+      """
+      POST /identity/basic/${{ identity.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Token ${{ identity.token }}
+      content-type: application/yaml
+
+      username: developer
+      password: secret#1234
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      """
+    When the following request is received:
+      """
+      DELETE /identity/basic/${{ identity.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Token ${{ identity.token }}
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    When the following request is received:
+      """
+      POST /identity/basic/${{ identity.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Token ${{ identity.token }}
+      content-type: application/yaml
+
+      username: painter
+      password: secret#4321
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      """
+    When the following request is received:
+      """
+      GET /identity/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic cGFpbnRlcjpzZWNyZXQjNDMyMQ==
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      id: ${{ identity.id }}
+      """

package/features/identity.federation.feature

@@ -54,6 +54,21 @@ Feature: Identity Federation
 
       id: ${{ User.id }}
       """
+    # credential id is detached from the Identity
+    When the following request is received:
+      """
+      GET /identity/federation/${{ User.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Bearer ${{ User.id_token }}
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      - id: ${{ User.credential }}
+        iss: http://localhost:44444
+      """
 
   Scenario: Creating an Identity using inception
     Given the `identity.federation` configuration:
@@ -88,8 +103,10 @@ Feature: Identity Federation
       """
       201 Created
       authorization: Token ${{ Bill.token }}
+
+      id: ${{ Bill.id }}
       """
-    # check that both tokens authenticate the created federation identity
+    # check that both tokens authenticate the created user's Identity
     When the following request is received:
       """
       GET /identity/ HTTP/1.1
@@ -100,6 +117,8 @@ Feature: Identity Federation
     Then the following reply is sent:
       """
       200 OK
+
+      id: ${{ Bill.id }}
       roles: []
       """
     When the following request is received:
@@ -113,8 +132,24 @@ Feature: Identity Federation
       """
       200 OK
 
+      id: ${{ Bill.id }}
       roles: []
       """
+    # credential id is detached from the Identity
+    When the following request is received:
+      """
+      GET /identity/federation/${{ Bill.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Bearer ${{ Bill.id_token }}
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      - id: ${{ Bill.credential }}
+        iss: http://localhost:44444
+      """
     And the following request is received:
       # same credentials
       """
@@ -214,6 +249,64 @@ Feature: Identity Federation
       content-type: application/yaml
       accept: application/yaml
 
+      scheme: bearer
+      credentials: ${{ Bob.id_token }}
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+
+      id: ${{ Bob.credential }}
+      iss: http://localhost:44444
+      """
+    # the created credential is listed as is
+    When the following request is received:
+      """
+      GET /identity/federation/${{ Bob.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic #{{ basic Bob }}
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      - id: ${{ Bob.credential }}
+        iss: http://localhost:44444
+      """
+    And the following request is received:
+      """
+      GET /identity/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Bearer ${{ Bob.id_token }}
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      id: ${{ Bob.id }}
+      """
+    # delete the federation credential
+    When the following request is received:
+      """
+      DELETE /identity/federation/${{ Bob.id }}/${{ Bob.credential }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic #{{ basic Bob }}
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    # add the same federation again
+    When the following request is received:
+      """
+      POST /identity/federation/${{ Bob.id }}/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic #{{ basic Bob }}
+      content-type: application/yaml
+      accept: application/yaml
+
       scheme: bearer
       credentials: ${{ Bob.id_token }}
       """

package/features/map.feature

@@ -269,6 +269,7 @@ Feature: HTTP context mapping
       """yaml
       trust:
         - iss: http://localhost:44444
+      assert: false
       """
     And the `pots` is running with the following manifest:
       """yaml
@@ -299,8 +300,8 @@ Feature: HTTP context mapping
       201 Created
 
       id: ${{ id }}
-      title: ${{ random.email }}
       volume: 1.5
+      title: ${{ random.email }}
       """
 
   Scenario: Mapping non-exposed properties

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toa.io/extensions.exposition",
-  "version": "1.0.0-alpha.254",
+  "version": "1.0.0-alpha.257",
   "description": "Toa Exposition",
   "author": "temich <tema.gurtovoy@gmail.com>",
   "homepage": "https://github.com/toa-io/toa#readme",
@@ -18,7 +18,7 @@
   },
   "dependencies": {
     "@simplewebauthn/server": "13.3.2",
-    "@toa.io/core": "1.0.0-alpha.254",
+    "@toa.io/core": "1.0.0-alpha.257",
     "@toa.io/generic": "1.0.0-alpha.254",
     "@toa.io/schemas": "1.0.0-alpha.254",
     "bcryptjs": "3.0.3",
@@ -62,5 +62,5 @@
     },
     "testEnvironment": "node"
   },
-  "gitHead": "0538900d6604e97d8850fad732bb56fd6be4f208"
+  "gitHead": "2db23a4e2ff6740a5f852208a9b896812ec6f819"
 }