@awiki/dsh-pap 0.0.0-stage → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +184 -2
- package/README.zh-CN.md +271 -0
- package/cordis.patch.yml +15 -0
- package/docs/verification.md +217 -0
- package/lib/auth-challenge.d.ts +19 -0
- package/lib/auth-challenge.js +136 -0
- package/lib/browser-client.js +81 -0
- package/lib/browser-client.js.map +6 -0
- package/lib/callback-handoff.d.ts +55 -0
- package/lib/callback-handoff.js +33 -0
- package/lib/client/controller.d.ts +107 -0
- package/lib/client/controller.js +106 -0
- package/lib/client/index.d.ts +6 -0
- package/lib/client/index.js +28 -0
- package/lib/client/views.d.ts +5 -0
- package/lib/client/views.js +57 -0
- package/lib/client.d.ts +108 -0
- package/lib/client.js +833 -0
- package/lib/cooldown.d.ts +11 -0
- package/lib/cooldown.js +88 -0
- package/lib/credential-history.d.ts +33 -0
- package/lib/credential-history.js +109 -0
- package/lib/delegation.d.ts +16 -0
- package/lib/delegation.js +59 -0
- package/lib/discovery.d.ts +8 -0
- package/lib/discovery.js +227 -0
- package/lib/errors.d.ts +14 -0
- package/lib/errors.js +17 -0
- package/lib/file-secrets.d.ts +14 -0
- package/lib/file-secrets.js +148 -0
- package/lib/host-secrets.d.ts +16 -0
- package/lib/host-secrets.js +22 -0
- package/lib/host.d.ts +83 -0
- package/lib/host.js +1 -0
- package/lib/index.d.ts +21 -0
- package/lib/index.js +13 -0
- package/lib/keyring.d.ts +10 -0
- package/lib/keyring.js +64 -0
- package/lib/management-remote.d.ts +13 -0
- package/lib/management-remote.js +69 -0
- package/lib/network.d.ts +23 -0
- package/lib/network.js +91 -0
- package/lib/plugin.d.ts +75 -0
- package/lib/plugin.js +473 -0
- package/lib/product-api.d.ts +89 -0
- package/lib/product-api.js +25 -0
- package/lib/product-operations.d.ts +16 -0
- package/lib/product-operations.js +120 -0
- package/lib/protocol-adapter.d.ts +90 -0
- package/lib/protocol-adapter.js +75 -0
- package/lib/remote.d.ts +3 -0
- package/lib/remote.js +17 -0
- package/lib/store.d.ts +14 -0
- package/lib/store.js +128 -0
- package/lib/strict-json.d.ts +2 -0
- package/lib/strict-json.js +111 -0
- package/lib/tools.d.ts +5 -0
- package/lib/tools.js +29 -0
- package/lib/types.d.ts +202 -0
- package/lib/types.js +1 -0
- package/lib/util.d.ts +17 -0
- package/lib/util.js +66 -0
- package/package.json +156 -4
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,3 +1,185 @@
|
|
|
1
|
-
#
|
|
1
|
+
# DSH PAP
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
**A PAP 0.3 client for DeepSeek Harness (DSH), powered by a reusable, locally held agent identity.**
|
|
4
|
+
|
|
5
|
+
English | [简体中文](README.zh-CN.md)
|
|
6
|
+
|
|
7
|
+
[PAP 0.3 specification](https://github.com/personal-agent-protocol/personal-agent-protocol/blob/6fb46d381ac1b94265795132af13848ec442b6f6/content/versions/0.3/spec.mdx) · [Shared identity](https://github.com/agent-network-protocol/anp-identity) · [Service Agent demo](https://github.com/AgentConnect/service-agent) · [Apache-2.0](LICENSE)
|
|
8
|
+
|
|
9
|
+
## The problem
|
|
10
|
+
|
|
11
|
+
A personal agent should be able to connect to independent service agents without registering a fresh identity and handling another private key at every service. This plugin lets a DSH agent **reuse an existing, user-authorized identity** for PAP Company discovery, Delegation, signed Sessions and approved business operations.
|
|
12
|
+
|
|
13
|
+
PAP is one of three complementary paths in the shared-identity system:
|
|
14
|
+
|
|
15
|
+
| Protocol | Identity and authentication | Integration |
|
|
16
|
+
| --- | --- | --- |
|
|
17
|
+
| **ANP** | Published `did:wba` identity; per-request HTTP signatures | [dsh-anp](https://github.com/agent-network-protocol/dsh-anp) |
|
|
18
|
+
| **MCP** | CIMD/JWKS client metadata; `private_key_jwt` and policy-approved `client_credentials` OAuth | [DSH MCP Host](https://github.com/AgentConnect/dsh-harness-identity) |
|
|
19
|
+
| **PAP 0.3** | Identity-signed Delegation and per-request `Poppy-Session`, with optional separate account authorization | **This plugin** |
|
|
20
|
+
|
|
21
|
+
One local identity anchors these protocol-specific credentials. **A PAP Session is not an MCP access token, and neither bypasses Company policy or account permissions.** Private signing keys stay with the local [ANP Identity](https://github.com/agent-network-protocol/anp-identity) Host, not with dsh-pap or a remote Company.
|
|
22
|
+
|
|
23
|
+
## Features
|
|
24
|
+
|
|
25
|
+
- Discover PAP Companies and advertised OpenAPI operations over constrained HTTPS.
|
|
26
|
+
- Create regular or anonymous signed-out Sessions and generate fresh PAP Delegation/Session proofs through the local identity Host.
|
|
27
|
+
- Enable only explicitly user-approved operations; the agent cannot choose arbitrary endpoints, methods, headers, tokens or scopes.
|
|
28
|
+
- Support **Direct Sign-In** when a Company requires an account: user-initiated OAuth authorization, PKCE, optional DPoP, protected token storage, refresh and sign-out.
|
|
29
|
+
- Store per-identity/Company Session and account state in encrypted local storage, using a Host secret provider, OS keyring or an explicitly selected protected local-file key store.
|
|
30
|
+
- Expose a DSH settings interface and narrowly scoped model tools.
|
|
31
|
+
|
|
32
|
+
The reference [ANP website Service Agent](https://agent.agent-network-protocol.com/ready) supports **signed-out PAP Sessions without an account or browser login**. A separate Company (for example a suitably configured Frontvia integration) is required to test account sign-in. The plugin does not automatically grant account access.
|
|
33
|
+
|
|
34
|
+
## Architecture
|
|
35
|
+
|
|
36
|
+
```text
|
|
37
|
+
DSH user / settings UI DSH Agent
|
|
38
|
+
| identity + Company | approved operation only
|
|
39
|
+
| selection / consent v
|
|
40
|
+
v pap_status / pap_operations / pap_request
|
|
41
|
+
PAP management Remote ---------> dsh-pap Host plugin
|
|
42
|
+
|
|
|
43
|
+
limited identity capability
|
|
44
|
+
|
|
|
45
|
+
ANP Identity (same Host)
|
|
46
|
+
local Delegation / Session / DPoP signing
|
|
47
|
+
|
|
|
48
|
+
signed HTTPS request
|
|
49
|
+
v
|
|
50
|
+
PAP Company
|
|
51
|
+
OpenAPI / business resources
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
The shared identity can publish DID, CIMD and JWKS material through an identity service such as [AWiki](https://awiki.me); its private keys remain on the client. The PAP plugin owns protocol state and account-token handling, but **does not load or export the Agent/Delegation/DPoP private keys**.
|
|
55
|
+
|
|
56
|
+
## Requirements and installation
|
|
57
|
+
|
|
58
|
+
- Node.js **^22.19.0 or >=24.0.0**.
|
|
59
|
+
- Compatible DSH Host (current integration targets DSH `0.2.2-rc.1`, Cordis `4.1.0`).
|
|
60
|
+
- [ANP Identity](https://github.com/agent-network-protocol/anp-identity) in the same Host, with a previously created and published identity and approved PAP consumer policy.
|
|
61
|
+
- A writable, private absolute `stateRoot` and working secret backend. The default is the Linux Secret Service / keyring; an explicit `local-file` backend supports additional platforms.
|
|
62
|
+
|
|
63
|
+
Install the bundle when its package is available in your registry:
|
|
64
|
+
|
|
65
|
+
```sh
|
|
66
|
+
pnpm dsh plugin --profile <profile> add @awiki/dsh-pap@0.1.1
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
Build and run unit/component checks from source:
|
|
70
|
+
|
|
71
|
+
```sh
|
|
72
|
+
git clone https://github.com/AgentConnect/dsh-pap.git
|
|
73
|
+
cd dsh-pap
|
|
74
|
+
npm ci --ignore-scripts
|
|
75
|
+
npm run typecheck
|
|
76
|
+
npm run build
|
|
77
|
+
npm test
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
The package exposes separate Host service, management Remote, tool and web-client entries. The bundled [Cordis patch](cordis.patch.yml) registers them **disabled by default**; installing the bundle alone does not sign requests or discover Companies. Ensure the installed package version is compatible with your ANP Identity Host API. Source/component verification is not a claim of completed production end-to-end acceptance.
|
|
81
|
+
|
|
82
|
+
## Configure the Host
|
|
83
|
+
|
|
84
|
+
Configure the **exact** installed identity consumer `@awiki/dsh-pap/plugin` in ANP Identity. The Host must approve the selected identity, purpose/policy, Company targets and scopes. The model cannot change these bindings.
|
|
85
|
+
|
|
86
|
+
Example Host plugin row:
|
|
87
|
+
|
|
88
|
+
```yaml
|
|
89
|
+
- id: pap
|
|
90
|
+
name: '@awiki/dsh-pap/plugin'
|
|
91
|
+
config:
|
|
92
|
+
enabled: true
|
|
93
|
+
stateRoot: /absolute/private/dsh/profile/pap
|
|
94
|
+
policyRef: approved-c-policy-id
|
|
95
|
+
keyringService: org.agentconnect.dsh-pap
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
If the default keyring is unavailable, **explicitly** select file-backed key storage. The two directories must be distinct, non-overlapping absolute paths:
|
|
99
|
+
|
|
100
|
+
```yaml
|
|
101
|
+
- id: pap
|
|
102
|
+
name: '@awiki/dsh-pap/plugin'
|
|
103
|
+
config:
|
|
104
|
+
enabled: true
|
|
105
|
+
stateRoot: /absolute/private/dsh/profile/pap
|
|
106
|
+
policyRef: approved-c-policy-id
|
|
107
|
+
secretStore: local-file
|
|
108
|
+
secretsRoot: /absolute/private/dsh/secrets/pap
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
On Windows use appropriate absolute paths (for example `C:/Users/...`). Never point both settings at the same directory. There is **no automatic fallback or migration** between secret backends. Preserve state and its matching encryption keys during backups or migrations. Old unpublished `@agentconnect/dsh-pap` consumer approvals do not automatically authorize the current `@awiki/dsh-pap/plugin` consumer.
|
|
112
|
+
|
|
113
|
+
## Try the live three-protocol service
|
|
114
|
+
|
|
115
|
+
After installation, shared identity publication and Host approval:
|
|
116
|
+
|
|
117
|
+
1. Open the DSH **PAP Company** settings and select an existing published identity.
|
|
118
|
+
2. Discover the Company at `agent.agent-network-protocol.com`. Its public metadata is at `https://agent.agent-network-protocol.com/.well-known/poppy.json`.
|
|
119
|
+
3. Connect a **signed-out** Session. Explicitly enable the discovered read operation (`protocol_list` or `protocol_get`) for the agent; optionally enable `post_create` for a deliberate posting test.
|
|
120
|
+
4. Ask the DSH agent to invoke `pap_status` and `pap_operations`. Use the returned operation reference in `pap_request`:
|
|
121
|
+
|
|
122
|
+
```text
|
|
123
|
+
pap_status()
|
|
124
|
+
pap_operations()
|
|
125
|
+
pap_request({
|
|
126
|
+
"operationRef": "<enabled post_create reference>",
|
|
127
|
+
"body": { "content": "Hello from DSH via PAP" }
|
|
128
|
+
})
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
The placeholder must be replaced by the **actual enabled operationRef**; the model cannot manufacture one. Read the published result on the [ANP website posts page](https://agent-network-protocol.com/zh/posts). Documentation can be read using the appropriate discovered read operation and its declared parameters.
|
|
132
|
+
|
|
133
|
+
**No user-account OAuth login is needed for this signed-out demo.** For Companies requiring an account, a user must explicitly start Direct Sign-In through the management UI, complete the Company's authorization, and enable the relevant account-bound operation. The agent cannot initiate a browser login or collect authorization codes.
|
|
134
|
+
|
|
135
|
+
## Tools and user controls
|
|
136
|
+
|
|
137
|
+
| Interface | Available operations |
|
|
138
|
+
| --- | --- |
|
|
139
|
+
| **Agent tools** | `pap_status`, `pap_operations`, `pap_request` only |
|
|
140
|
+
| **User management** | `identity/select`, `company/discover`, `session/connect`, `session/disconnect`, `operation/enable`, `operation/disable` |
|
|
141
|
+
| **Account management** | `account/sign-in`, `account/collect`, `account/refresh`, `account/sign-out` |
|
|
142
|
+
|
|
143
|
+
The management Remote must be exposed only through an authenticated **user** gateway, never as a general model tool. Agent calls accept a previously authorized `operationRef` plus declared path/query fields and an optional JSON body; they do not accept arbitrary URL/method/headers, raw authorization tokens or resource changes.
|
|
144
|
+
|
|
145
|
+
## Service Agent example
|
|
146
|
+
|
|
147
|
+
https://agent-network-protocol.com is the project's example Service Agent for
|
|
148
|
+
MCP, ANP and PAP. The example is mentioned in the Agent-visible discovery/status
|
|
149
|
+
tool descriptions. To see ANP in action, discover `agent-network-protocol.com`,
|
|
150
|
+
read the returned descriptions/interfaces, then invoke a read-only discovered
|
|
151
|
+
operation. For PAP, explicitly discover that Company in settings, connect and
|
|
152
|
+
enable the desired operation. MCP uses a separately configured server connection.
|
|
153
|
+
No reference here grants identity access, enables an operation, bypasses protocol
|
|
154
|
+
validation, or sends a request automatically. The website deployment is managed
|
|
155
|
+
by the service operator and is outside this UI change's acceptance scope.
|
|
156
|
+
|
|
157
|
+
## Basic and advanced settings
|
|
158
|
+
|
|
159
|
+
The normal PAP page shows the active published identity, Company discovery,
|
|
160
|
+
one regular connection and explicit operation permission. Existing regular
|
|
161
|
+
connections are reused by the UI rather than creating duplicates. Connection
|
|
162
|
+
IDs/cleanup, per-operation connection changes, scopes and optional account
|
|
163
|
+
management are collapsed by default. NoAS companies do not show account-login
|
|
164
|
+
controls. Existing sessions are never deleted automatically, accounts/scopes are
|
|
165
|
+
never selected implicitly, and saving a different operation connection remains
|
|
166
|
+
an explicit user action.
|
|
167
|
+
|
|
168
|
+
## Security and current limits
|
|
169
|
+
|
|
170
|
+
- PAP state is AES-256-GCM encrypted and partitioned by identity/profile. Missing or mismatched secret keys fail closed.
|
|
171
|
+
- Local identity custody provides scoped, revocable signing capabilities; this plugin does not expose the private keys or a remote signing endpoint.
|
|
172
|
+
- Signed-out PAP makes no account-authority claim; account OAuth is explicit and separate from MCP machine tokens.
|
|
173
|
+
- Side-effecting requests are not blindly replayed after ambiguous failures. Token rotation, disconnect and sign-out enforce state and authorization fences.
|
|
174
|
+
- Browser Join, Mediated Sign-In, Device Sign-In, PS384, automatic account merging and a PAP-over-MCP transport are **not implemented** in this client.
|
|
175
|
+
- Existing legacy account state may require a controlled migration/revocation review; do not reset encrypted state or silently create replacement encryption keys.
|
|
176
|
+
|
|
177
|
+
For detailed API, storage, verification and recovery notes see the [Chinese technical README](README.zh-CN.md), [verification log](docs/verification.md) and [source code](src/).
|
|
178
|
+
|
|
179
|
+
## Related projects
|
|
180
|
+
|
|
181
|
+
[ANP Identity](https://github.com/agent-network-protocol/anp-identity) · [dsh-anp](https://github.com/agent-network-protocol/dsh-anp) · [service-agent](https://github.com/AgentConnect/service-agent) · [DSH Harness Identity](https://github.com/AgentConnect/dsh-harness-identity) · [AWiki User Service](https://github.com/AgentConnect/user-service)
|
|
182
|
+
|
|
183
|
+
## License
|
|
184
|
+
|
|
185
|
+
[Apache-2.0](LICENSE).
|