mozilla-iam / mozilla-iam/auth0-deploy
Set assetsUrl conditionally on whether the code is being run in a free or enterprise auth0 account
Open
Nobody has claimed this yet.
Auth0 Lock
enhancement
wontfix
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 21
- Avg merge
- 17h 49m
- Merged PRs (30d)
- 5
Description
Currently the assetsUrl in the hosted lock code is configured for use on our private appliance/enterprise. When you copy paste the code into a free auth0 account it doesn't work.
- Determine what this is dependent on, be it enterprise vs not enterprise or public cloud vs private instance
- Determine if there's a way to divine which environment we're in when the code runs
- Modify the hosted lock to conditionally set the
assetsUrlbased on that.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the hosted lock code and its assetsUrl configuration. Determine whether the value depends on an enterprise account, public cloud, or private instance, and whether the running code can identify that environment. Done means the hosted lock works when copied into both free Auth0 accounts and enterprise deployments with the appropriate assetsUrl.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100