AEP Web SDK Configuration View - Data Element :: XDM Object requires AEP Schema Registry Permissions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reproducing the failure in the AEP Web SDK Configuration View for the Data Element :: XDM Object with a user who lacks AEP Schema Registry permissions, then inspect the schema API calls made while selecting the sandbox and schema. Done means the view no longer fails to render and displays a message describing the required permissions when those calls return an error.
Written by the indexing model from the issue text.
Description
Expected Behaviour
When rendering the "AEP Web SDK" Configuration View - Data Element :: XDM Object, there are API calls to pull in schema information. If the Launch user doe not have the appropriate permissions for these API calls, the extension view fails to render. At a minimum, the API response code should be caught and a message indicating the required permissions should be displayed.
Actual Behaviour
If the Launch user doe not have the appropriate permissions to get AEP Schema info, the extension view fails to render.
Reproduce Scenario (including but not limited to)
Find two users with access to Adobe Experience Platform Launch Data Collection, by Adobe.
Assure that one user has access to view AEP Schemas
Assure that the other user does not have access to view AEP Schemas
Have the first user create an AEP Web SDK :: XDM Object Data Element (selecting Sandbox and Schema).
Have the second user attempt to edit that data element.
Boom.
IDK what happens if both users have AEP schema access but different sandbox access. I would assume that a similarly bvad situation exists.
Steps to Reproduce
See above.
Platform and Version
Adobe Experience Platform Launch Data Collection, by Adobe.
Sample Code that illustrates the problem
Logs taken while reproducing problem
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 63
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/alloy
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
adobe/alloy#1323 · 3 comments ·
Maintainers usually reply within 1 day
-
3.0.0Openbranch:main release
Difficulty 5/5 Over a week Newbie friendliness 15/100
adobe/alloy#1170 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 32/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
adobe/alloy#1021 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
adobe/alloy#970 · 6 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
postcss/postcss.org#302 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ImranR98/apps.obtainium.imranr.dev#2000 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
microsoft/monaco-editor#5577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Ebony-Vinyl/dsh-our-free-model#785 ·
Maintainers usually reply within 1 day