# Auth0 rules testing using webtask token

**URL:** <https://community.auth0.com/t/auth0-rules-testing-using-webtask-token/11036>\
**Category:** Get Help\
**Tags:** test, rules, webtask\
**Created:** [April 20, 2018, 8:20am UTC](https://community.auth0.com/t/auth0-rules-testing-using-webtask-token/11036 "2018-04-20T08:20:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenneth.leine.schuls](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/kenneth.leine.schuls/32/8458_2.png) [@kenneth.leine.schuls](https://community.auth0.com/u/kenneth.leine.schuls)\
**Post date:** [April 20, 2018, 8:20am UTC](https://community.auth0.com/t/auth0-rules-testing-using-webtask-token/11036/1 "2018-04-20T08:20:41Z")

</div>

I’m writing some auth0 rules tests, based on this:

> **[GitHub - tawawa/auth0-rules-testharness-sample: Seed project for auth0-rules-testharness to help...](https://github.com/tawawa/auth0-rules-testharness-sample)**
>
> Seed project for auth0-rules-testharness to help users get started immediately

The auth0-rules-testharness library provides a way to deploy, execute, and test the output of Auth0 Rules using a real webtask sandbox environment. To access my tenant’s webtask environment I need an access token.

The wording in the auth0-rules-testharness docs goes something like this:  
token: the webtask token. You can get your webtask token from [your auth0 dashboard.](https://manage.auth0.com/#/tenant/webtasks) (suggesting that the access token does not expire)

Also, this post suggests the same (that is: non-expiring webtask accessToken):

> [@Webtask credentials for deployment pipeline](http://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981):
>
> We prefer having an automated process to deploy anything. I’ve been looking at options to deploy an Auth0 Hook from my build pipeline. The Tenant settings show a way to initialise the wt-cli ([https://manage.auth0.com/#/tenant/webtasks](https://manage.auth0.com/#/tenant/webtasks)), however the token shown doesn’t seem to have an expiry, or a way to revoke it, and is not contextualised to the currently logged in auth0 user… I’ve looked at using wt init without a token, however that does not seem capable of linking to an Auth0 Tenant… Does…

However, in the auth0 dashboard, I only see instructions like:

> wt init …

Following these instructions, I am able to generate an access token (can be found in ~/.webtask), however this access token is only valid for approx 12ish hours.

So.. for the questions:

1. Is the non-expiring webtask accessToken something that _used to be_ available (and is no longer)?
2. Can I find an accessToken elsewhere?

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [December 18, 2018, 5:38pm UTC](https://community.auth0.com/t/auth0-rules-testing-using-webtask-token/11036/3 "2018-12-18T17:38:12Z")

</div>

Hey @kenneth.leine.schuls

As it has been more than a few months since this topic was opened and there has been no reply or further information provided from the community as to the existence of the issue we would like to check if you are still facing the described challenge?

We are more than happy to assist in any way! If the issue is still out there please let us know so we can create a new thread for better visibility, otherwise we’ll close this one in week’s time.

Thank you!

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [December 25, 2018, 9:38am UTC](https://community.auth0.com/t/auth0-rules-testing-using-webtask-token/11036/4 "2018-12-25T09:38:16Z")

</div>

This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.
