Rhythm 2.0 Specifications

Appearance

FAS-PFM-INT-02Provider accounts and credentials acceptance

Markdown

FAS-PFM-INT-02

Provider accounts and credentials acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-INT-02
Capabilities
CAP-PFM-INT-004, CAP-PFM-INT-005, CAP-PFM-INT-006

Product areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision2

Read atservices-platform ad3f6a65macroservice-libraries 54536a44react-console baf6dae3

Provider accounts and credentials: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The suite follows account setup, verification and recovery alongside health and credential handling. Acceptance inspects the account a person can operate and the safe detail they can read after each change.

Interactions Between Capabilities ​

A refresh refusal affects connection eligibility, visible attention and notices. Replacement and disconnection cases inspect those effects together with credential retirement, while the permission case separates account management from authority to replace secrets.

The reliance links identify detailed capability scenarios. None of these composed acceptance sequences has a verified executable binding at the pinned revisions; the corresponding coverage finding remains open.

Regression Record ​

RevisionChangeScenariosReason
1InitialAllEstablish the cumulative acceptance sequences and initial regression cases.
2Testing examination continuationAllClarify the feature boundary and preserve proposed status for unbound composed sequences.

Scenarios

5 scenarios proving FEAT-PFM-INT-02 as a whole.

01 A verified account has safe operational detail behaviour proposed
Exercises
CAP-PFM-INT-004 CAP-PFM-INT-005 CAP-PFM-INT-006
Relies on
ATS-PFM-INT-004-01 ATS-PFM-INT-005-01 ATS-PFM-INT-006-01
Preconditions
An enabled installation supports an entered key.
Steps
Create an account, enter a valid key, complete verification and inspect credential facts and health.
Expected
The usable account and its health are visible without the key value.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#connects a platform account, which starts verifying with its job,services-platform:modules/integrations/tests/integration/services/credentials/credential-state.integration.spec.js#answers no secret value, secret name or key version,react-console:lib/integrations/connection-dot.test.ts#is grey for suspended and disconnected, whatever the last health check said
02 Refresh refusal becomes visible account attention interaction proposed
Exercises
CAP-PFM-INT-004 CAP-PFM-INT-005 CAP-PFM-INT-006
Relies on
ATS-PFM-INT-005-10 ATS-PFM-INT-006-03
Preconditions
An active account has a token due for refresh.
Steps
Return authorization refusal during refresh and inspect account detail, attention and notices.
Expected
Re-authorization is required and the visible reason follows the saved provider refusal.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/credentials/refresh.integration.spec.js#makes one token request when two refreshes of a connection run at once,services-platform:modules/integrations/tests/integration/services/connections/connection-jobs.integration.spec.js#degrades an active connection whose provider is unhealthy
03 Disconnect retains safe history and schedules secret cleanup lifecycle proposed
Exercises
CAP-PFM-INT-004 CAP-PFM-INT-005 CAP-PFM-INT-006
Relies on
ATS-PFM-INT-004-09 ATS-PFM-INT-005-04
Preconditions
A verified account has credentials and no current bindings.
Steps
Disconnect it, inspect its history and credential state, then run maintenance after the recovery period.
Expected
Closure is retained, secret cleanup completes when storage reports deletion and history exposes no secret value.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/connections/transition.integration.spec.js#disables the connection’s webhook endpoints,services-platform:modules/integrations/tests/integration/services/credentials/credential-lifecycle.integration.spec.js#INT-ACC-0163 step 5: svc_accounting’s payments.authorize right after the replacement, before the re-verification runs, leases the new credential
04 Account management does not imply secret authority permissionnegative proposed
Exercises
CAP-PFM-INT-004 CAP-PFM-INT-005 CAP-PFM-INT-006
Relies on
ATS-PFM-INT-005-02 ATS-PFM-INT-004-02
Preconditions
A reader and account manager without credential permission inspect one account.
Steps
Read account health and credential facts, then attempt key replacement as the manager.
Expected
Safe inspection succeeds while the unauthorized replacement leaves the account and credential unchanged.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
services-platform:modules/integrations/tests/e2e/credentials.e2e.spec.js#is refused to a caller who manages connections but not their credentials,services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#refuses a second connection of the tenant whose name derives to a taken id, 409 naming the id
05 Correct a refused account credential regressionnegative proposed
Exercises
CAP-PFM-INT-004 CAP-PFM-INT-005 CAP-PFM-INT-006
Relies on
ATS-PFM-INT-004-05 ATS-PFM-INT-005-05 ATS-PFM-INT-006-01
Preconditions
An initial key is rejected during verification.
Steps
Inspect the failure, replace it with a valid key and complete verification.
Expected
The account recovers to active with features and the expected health indicator.
Data
Run-owned declarations, records and role fixtures in an isolated workspace.
Source
FND-PFM-INT-034,services-platform:modules/integrations/services/credentials/credential-store.ts:verification_retried,react-console:lib/integrations/connection-dot.test.ts#is grey for suspended and disconnected, whatever the last health check said

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software