Remove jenkins file

.circleci/config.yml

@@ -7,7 +7,7 @@ jobs:
   build:
     docker:
       # specify the version you desire here
-      - image: circleci/node:boron
+      - image: node:erbium
 
       # Specify service dependencies here if necessary
       # CircleCI maintains a library of pre-built images
@@ -26,12 +26,14 @@ jobs:
           # fallback to using the latest cache if no exact match is found
           - v1-dependencies-
 
-      - run: yarn install
+      - run: yarn
 
       - save_cache:
           paths:
             - node_modules
           key: v1-dependencies-{{ checksum "package.json" }}
 
       # run tests!
+      - run: yarn run lint
       - run: yarn test
+      - run: ./test/bundle_test.sh

.eslintignore

@@ -0,0 +1,6 @@
+node_modules/**
+integration/**
+sample-app/**
+build/**
+test/**
+dist/**

.eslintrc

@@ -7,7 +7,8 @@
     "mocha": true
   },
   "rules": {
+    "jsx-a11y/href-no-hash": "off",
+    "import/no-extraneous-dependencies": "off"
   },
-  "plugins": [
-  ]
+  "plugins": []
 }

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,62 @@
+## ✏️ Changes
+
+> DESCRIPTION GOES HERE. Try to describe both what is changing and why this is important
+> - Make sure you run  when adding / updating a package
+> - What did you change from a design standpoint?
+> - What did you change in the code itself?
+> - If you are updating a dependency, explain why this is needed.
+
+## 📷 Screenshots
+
+If there were visual changes to the application with this change, please include before and after screenshots here. If it has animation, please use screen capture software like  to make a gif.
+
+## 🔗 References
+
+> Include at at least one link to an explanation + requirements for this change, and more if at all possible. Typically this is a Jira/GitHub Issue, but could also be links to Zendesk tickets, RFCs, rollout plan or Slack conversations (for Slack conversations, make sure you provide a summary of the conversation under “Changes”).
+
+## 🎯 Testing
+
+> Describe how this can be tested by reviewers. Please be specific about anything not tested and reasons why.
+> - Make sure you add unit and integration tests.
+> - If this is on a hot path, add load or performance tests
+> - Especially for dependency updates we also need to make sure that there is no impact on performance.
+
+✅🚫 This change has been tested in a Webtask
+
+✅🚫 This change has unit test coverage
+
+✅🚫 This change has integration test coverage
+
+✅🚫 This change has been tested for performance
+
+## 🚀 Deployment
+
+> Can this change be merged at any time? What will the deployment of the change look like? Does this need to be released in lockstep with something else?
+
+✅🚫 This can be deployed any time
+
+> or
+> ⚠️ This should not be merged until:
+> - Other PR is merged because REASON
+> - After date because REASON
+> - Other condition: REASON
+
+## 🎡 Rollout
+
+> Explain how the change will be verified once released. Manual testing? Functional testing?
+
+In order to verify that the deployment was successful we will …
+
+## 🔥 Rollback
+
+> Explain when and why we will rollback the change.
+
+We will rollback if …
+
+### 📄 Procedure
+
+> Explain how the rollback for this change will look like, how we can recover fast.
+
+## 🖥 Appliance
+
+**Note to reviewers:** ensure that this change is compatible with the Appliance.

.github/stale.yml

@@ -0,0 +1,2 @@
+# Configuration for https://github.com/auth0-extensions/.github/
+_extends: .github

.github/workflows/semgrep.yml

@@ -0,0 +1,18 @@
+name: Semgrep
+
+on:
+  pull_request_target: {}
+  push:
+    branches: ["master", "main"]
+jobs:
+  semgrep:
+    name: Scan
+    runs-on: ubuntu-latest
+    container:
+      image: returntocorp/semgrep
+    if: (github.actor != 'dependabot[bot]' && github.actor != 'snyk-bot')
+    steps:
+      - uses: actions/checkout@v3
+      - run: semgrep ci
+        env:
+          SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}

.gitignore

@@ -1,11 +1,16 @@
 node_modules
+.idea
 .DS_Store
 .nyc_output
 server/config.json
 server/config.test.json
 coverage
 .env
-dist
+dist/*.js
+dist/assets/*.css
 tags
 TAGS
-data.json
+data.json
+*.swp
+yarn-error.log
+secrets

CODEOWNERS

@@ -0,0 +1,2 @@
+# Code owners are automatically requested for review when someone opens a pull request that modifies code that they own.
+*    @auth0-extensions/iam-user-management-engineer

CONTRIBUTING.md

@@ -0,0 +1,39 @@
+
+# Contributing to Auth0 projects
+
+A big welcome and thank you for considering contributing to the Auth0 projects. It’s people like you that make it a reality for users in our community.
+
+Reading and following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing these open source projects. In return, we will reciprocate that respect by addressing your issue.
+
+### Quicklinks
+
+* [Code of Conduct](#code-of-conduct)
+* [Getting Started](#getting-started)
+    * [Making Changes](#making-changes)
+* [Getting in Touch](#getting-in-touch)
+    * [Got a question or problem?](#got-a-question-or-problem?)
+    * [Vulnerability Reporting](#vulnerability-reporting)
+
+## Code of Conduct
+
+By participating and contributing to this project, you are expected to uphold our [Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md).
+
+## Getting Started
+
+### Making Changes
+
+To contribute to a repository, the first step is to open a support ticket
+
+[Opening a ticket] (https://auth0.com/docs/troubleshoot/customer-support/open-and-manage-support-tickets).
+
+## Getting in touch
+
+### Have a question or problem?
+
+Please do not open issues for general support or usage questions. Instead, join us over in the Auth0 community at [community.auth0.com](https://community.auth0.com) and post your question there in the correct category with a descriptive tag.
+
+### Vulnerability Reporting
+
+Please do not report security vulnerabilities on the public GitHub issue tracker. The [Responsible Disclosure Program](https://auth0.com/whitehat) details the procedure for disclosing security issues.
+
+# More Information about this service is located in README.md at the root of this repository

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016 Auth0
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -15,22 +15,23 @@ with an existing registered with the same email address from a different provide
 
 ## Running in Development
 
-
 Update the configuration file under `./server/config.json`:
 
 ```json
 {
-	"EXTENSION_SECRET": "mysecret",
-	"AUTH0_DOMAIN": "me.auth0.com",
-	"AUTH0_CLIENT_ID": "myclientid",
-	"AUTH0_CLIENT_SECRET": "myclientsecret",
-    "WT_URL": "http://localhost:3000"
+  "EXTENSION_SECRET": "mysecret",
+  "AUTH0_DOMAIN": "me.auth0.com",
+  "AUTH0_CLIENT_ID": "myclientid",
+  "AUTH0_CLIENT_SECRET": "myclientsecret",
+  "WT_URL": "http://localhost:3000",
+  "AUTH0_CALLBACK_URL": "http://localhost:3000/callback"
 }
 ```
 
 Then you can run the extension:
 
 ```bash
+nvm use 8
 yarn install
 yarn run build
 yarn run serve:dev
@@ -43,4 +44,24 @@ In order to run the tests you'll have to [start the extension server locally](ht
 Then, you can run the tests running:
 ```bash
 yarn test
-```
+```
+
+## Release Process
+
+Deployment is currently done using this tool: https://auth0-extensions.us8.webtask.io/extensions-deploy
+
+First bump the version in `package.json` and in `webtask.json`
+
+Then build the extension:
+
+```bash
+nvm use 8
+yarn install
+yarn run build
+```
+
+Bundle file (`auth0-account-link.extension.VERSION.js` is found in `/dist`
+Asset CSS files are found in `/dist/assets`
+
+Follow the instructions in the deployment tool.  This tool will also automatically generate a PR in the `auth0-extensions` repo.  Only after the PR is merged will the extension be available in production.  Before merging the PR you can use this tool to test the upgrade: https://github.com/auth0-extensions/auth0-extension-update-tester by overriding the `extensions.json` file that is fetched by the dashboard.  You will need to clone this repo: https://github.com/auth0/auth0-extensions, update `extensions.json` locally and then run `npx http-server --port 3000 --cors` to serve up the file.  Then configure the extension with `http://localhost:3000/extensions.json` as the path.
+

api/admin/get_index.js

@@ -1,5 +1,6 @@
-import tools from 'auth0-extension-tools';
-import config from '../../lib/config';
+const template = require('../../templates/server/admin');
+const config = require('../../lib/config');
+const stylesheet = require('../../lib/stylesheet');
 
 module.exports = () => ({
   method: 'GET',
@@ -8,6 +9,8 @@ module.exports = () => ({
     auth: false
   },
   handler: (req, reply) => {
-    reply.view('admin');
+    const stylesheetHelper = stylesheet(config('NODE_ENV') === 'production');
+
+    reply(template({ stylesheetTag: stylesheetHelper.tag('admin'), baseURL: config('PUBLIC_WT_URL') }));
   }
 });

api/admin/get_locale_index.js

@@ -0,0 +1,18 @@
+const template = require('../../templates/server/locale');
+const config = require('../../lib/config');
+const stylesheet = require('../../lib/stylesheet');
+
+module.exports = () => ({
+  method: 'GET',
+  path: '/admin/locale',
+  config: {
+    auth: false
+  },
+  handler: (req, reply) => {
+    const stylesheetHelper = stylesheet(config('NODE_ENV') === 'production');
+
+    reply(
+      template({ stylesheetTag: stylesheetHelper.tag('admin'), baseURL: config('PUBLIC_WT_URL') })
+    );
+  }
+});