ADP takes per-org credentials, not a platform registration

Fixkamo-shared-library
Ya
14 Agosti 2026, 01:18 UTC
Mwandishi
Kamo
Ahadi ya
c187245

ADP shipped classified PLATFORM_OAUTH on the strength of ADP publishing a Marketplace ISV model, where Kamo would hold one partner client id, secret and certificate and retrieve each customer's credentials with the partner token. That path is not implemented. AdpWorkforceNowProvider builds its mutual-TLS client from adpClientCertPem / adpClientKeyPem in the organization's own config and never consults PlatformOAuthClientResolver — it is the only adapter that never calls **************** So the classification put a Connect button and a platform credentials card in front of operators that nothing read: paste a certificate, watch it save, and every ADP call still fails for a missing per-org field. Reclassified PER_ORG_CREDENTIALS with no registration. PlatformOAuthProviderType .ADP_WFN(17) stays — ids there are persisted and the enum is append-only — but is now documented as RESERVED, with an explicit warning not to add a card for it until the Marketplace path exists.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei