authgear / authgear/authgear-server
UX improvement on CORS hints / input at Applications page
- Dominant language
- Go
- Stars
- 2k
- Forks
- 125
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 32
Description
**Describe the bug**
Not exactly a bug, but a potential UX issues.
When users encounter a CORS error when they create a webapp sign in with Authgear, they might not be able to co-relate the URL added to "Authorized Redirect URIs" would be automatically added to CORS list as well.
To enable developers to debug / learn about it faster, we shall consider:
1. Add CORS and related keywords at the page of **Authorized Redirect URIs**
2. Add a section in the (Application?) page such that users can manually add URL for CORS allow list
Contributor guide
Research direction
Start at the Applications page and inspect the Authorized Redirect URIs section, using the linked screenshot to understand the current UX. Confirm the intended CORS terminology and whether a separate allow-list input is required; done means the relationship is discoverable and the requested CORS URL configuration is usable.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100