FRW-11887 Merchant user authentication for the Backend API - #3899
Draft
demkos wants to merge 8 commits into
Draft
Conversation
* Add the "Authenticate as a merchant user" page for POST /token and the roles the token grants. * Document the back-office-user and merchant-user scope to role mapping and the resource-level security requirement. * Document resolving the user behind a token and the UserIdentityCriteriaExpanderPluginInterface extension point. * Add the optional Persistent ACL wiring for the Backend API to the API Platform security integration guide.
✅ Deploy Preview for spryker-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4 tasks
…ire the API Platform integration
…clEntity plugin namespace
…PI Platform endpoint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
Documents the merchant user authentication for the Backend API shipped with spryker/suite#1062:
POST /token, JSON:API body, the scopes and roles the token grants, the active-user requirement, possible errors), linked from the Back Office authentication page and the sidebar.back-office-user→ROLE_BACK_OFFICE_USERandmerchant-user→ROLE_MERCHANT_USERscope mapping (hyphens become underscores,usermaps to no role), a new Resolving the user behind a token section with theUserIdentityCriteriaExpanderPluginInterfaceextension point, and a warning that Bearer authentication only runs for resources that declaresecurityat the resource level.MerchantUserTypeOauthScopeProviderPluginand the hyphen rule of the mapping.AclEntityApplicationPlugin+NoCurrentUserAclEntityDisablerPlugin).Ready for review once spryker/suite#1062 is merged; opened as a draft until then.
Scope note: everything documented here requires the API Platform integration of the Backend API; the legacy Glue infrastructure is not covered, and every page says so in an info block.
Tickets
FRW-11887 — https://spryker.atlassian.net/browse/FRW-11887 (code: spryker/suite#1062)
Checklist