-
Notifications
You must be signed in to change notification settings - Fork 58
fix: add org level permissions to new org #707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
* feat: auto submit form if org and site are provided * chore: provide feedback if error
| const body = new FormData([['config', JSON.stringify(configJson)]]); | ||
| const orgResp = await daFetch(orgUrl, { method: 'PUT', body }); | ||
| if (!orgResp.ok) { | ||
| if (orgResp.status === 401 || orgResp.status === 403) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this really happen ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it prudent to check for... unless we fully trust the window.adobeIMS.isSignedInUser() above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was more thinking on the api side. If you have a token, the config api should let you in. At least for the moment...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if the org already exists with different permissions?
Fix #415
https://i415--da-live--adobe.aem.page/