Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. On Premises
  2. AWS
  3. Configure your instance

Configure Auth0

PreviousCreate a PostgreSQL instanceNextConfigure API

Last updated 2 years ago

Was this helpful?

You need a free Auth0 account to manage your Taskforce.sh users. Login in auth0 and create a new application:

Choose "Single Page Web Application"

Go to the App Settings and configure the callbacks:

Assuming the URI to access your instance is onpremises.taskforce.sh you will need to configure the callbacks like these:

You also need to configure the Allowed Web Origins and Allowed Origins (CORS):

You can leave the rest of the settings on their defaults.

Note that you should pick the "clientId" and the "domain" from this application and use them in your Taskforce instance settings:

Auth0 Application Settings
Taskforce.sh on-premises configuration