Description
Support a new external-service authentication_type — DIAL Native — where the application acts on behalf of users through their own offline credentials instead of a stored credential.
There is nothing to sign in with, so these rows have no Log in action. A DIAL administrator grants consent for the application instead. One approval covers every user in the installation who has enabled offline access — not only the users of that application, so the row and its dialogs say so explicitly.
Existing authentication types keep their current behaviour.
Key points:
- DIAL Native rows offer
Grant consent, or an Approved badge plus Withdraw consent. No Log in action in any state
- Both actions require confirmation, stating the installation-wide reach
- Consent is admin-only, and is the row's only mutation: no Edit or Delete, since renaming the Service ID would orphan the approval
OAUTH, API_KEY and NONE rows are unchanged
Related issues
epam/ai-dial-core#1815 — provides the consent endpoints and the DIAL_NATIVE type
Confidential information
Description
Support a new external-service
authentication_type— DIAL Native — where the application acts on behalf of users through their own offline credentials instead of a stored credential.There is nothing to sign in with, so these rows have no
Log inaction. A DIAL administrator grants consent for the application instead. One approval covers every user in the installation who has enabled offline access — not only the users of that application, so the row and its dialogs say so explicitly.Existing authentication types keep their current behaviour.
Key points:
Grant consent, or anApprovedbadge plusWithdraw consent. NoLog inaction in any stateOAUTH,API_KEYandNONErows are unchangedRelated issues
epam/ai-dial-core#1815 — provides the consent endpoints and the
DIAL_NATIVEtypeConfidential information