Jump to content

Auth0 Login (Changes)


Recommended Posts

Hello everyone,

Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

Important changes

  • When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials
    • Note: 2FA is still handled through your forums account (for the time being)

Changes for existing users

Important notes

  • Make sure to verify your email address upon creating a new Auth0 account
  • When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below

image.png.a28ac6835d296e611ca1a505ba1f27db.png

Link to post
Share on other sites
  • Replies 81
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I CANT FUCKING LOGIN TO CLIENT AT ALL FFS HOW THE FUCK CAN YOU FUCK UP SO BAD? FIX THIS SHIT IM PAYING MONEY AND IN RETURN HAVE NOTHING. FFS.

Would it be at all possible to perhaps get the devs to hire someone to act as the community liason? Someone who can be more accountable than the devs to interact, communicate, and be the face of the c

I have the same problem i just changed my password. I can login on the website but not on the client, then ill tried my old password and that one makes the client load for some reason.

4 minutes ago, simongek said:

I have the same problem i just changed my password. I can login on the website but not on the client, then ill tried my old password and that one makes the client load for some reason.

 

 

 

My auth0 is my email right? cause it wont let me login on tribot with my email iam confused english is not my first language to that can aswell be the reason haha

Link to post
Share on other sites
1 hour ago, Todd said:

Hey everyone, we're very aware of a select group of people having issues and we're working to solve it!

@Todd @TRiLeZ not to be a party pooper, but why is it hard for you guys to implement an actual QA/Testing environment. Release a modified client to test, and leave production alone when you make carelessly planned changes like these? I'm a huge fan of the work, and the product, but this is crazy... It's an entire day of downtime at this point all to cutover to your untested auth systems.

If it's a matter of resources, I operate cloud hosting infrastructure, would be happy to work something out here.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Our picks

    • We've heard your complaints - the TRiBot API could be much easier to use. We've been dedicating our time to improving the scripter experience here and spent the past year working on a new and improved API - the TRiBot Script SDK.

       

      The TRiBot Script SDK is an easy-to-use library for building TRiBot scripts. It is the recommended approach to building scripts moving forward over the old TRiBot API. It contains all the core things you need to build a script, and a ton of additional helpful stuff to get you using your scripts quicker. See the documentation section for everything offered, and check out the brief overview link too.

       

      The SDK was announced in preview here:

       

      It is now officially released. The official release guarantees we will support backwards compatibility for some period of time. See the 'backwards compatibility' section below for more info.

       

      How to use:

      There is multiple options, listed in the order they are recommended.

      1) Use the gradle template mentioned below

      2) Obtain through gradle

      Add this dependency: api("org.tribot:tribot-script-sdk:+")

      Add this repository: maven("https://gitlab.com/api/v4/projects/20741387/packages/maven")

      3) Take from your local filesystem in your .tribot/install folder. For example, on windows, you'd find it at "C:\Users\[user]\AppData\Roaming\.tribot\install\tribot-client\lib\tribot-script-sdk-[version].jar"

       

      Documentation:

      Java docs: https://runeautomation.com/docs/sdk/javadocs/index.html?overview-summary.html

      Kotlin docs: https://runeautomation.com/docs/sdk/kdocs/index.html

       

      Backwards compatibility:

      We will be following a deprecation schedule whenever we perform a possible breaking change. We will deprecate the respective methods or classes and announce it in a topic. It will remain deprecated for some period of time (weeks or months), and then removed. This will give you time to fix anything, if we need to make a breaking change.

       

      Gradle template:

      Easily build scripts with a new pre-configured scripting gradle template

       

      Users of the current API:

      There is no plans to remove TRiBot API. It will still be available. However, non-critical bugs probably won't be fixed. The SDK does depend on some of the API so fixing some things in the SDK will indirectly fix the API. However, bugs that have existed in the API for awhile will likely not be fixed. It's recommended to use the SDK moving forward. Let us know if there's something the SDK is missing.

       

      Brief overview of the changes:

       

      Bug reports:

      Post bug reports in the bug reports section of the forums

       

       

      Let us know what your thoughts are! If you have questions, feel free to ask below or in discord.

       
      • 0 replies
    • Support for the gradle launcher is being dropped. Read more about the new launcher here.
      • 8 replies
    • What to expect from TRiBot moving forward.
        • Like
      • 11 replies
    • TRiBot 12 Release Candidate

      The TRiBot team has been hard at work creating the last major version of TRiBot before the TRiBot X release. We've noticed many problems with TRiBot 11 with a lot of users preferring TRiBot 10 over 11. We've heard you, so we took TRiBot 10, added the new features introduced with 11, introduced some other new things, and created TRiBot 12. So without further adieu, here's TRiBot 12.
      • 40 replies
    • Gradle is a build tool used to accelerate developer productivity.

      We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

      Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

      The goals of TRiBot Central are to:

      Deliver updates to TRiBot faster


      Better organize TRiBot's dependencies (AKA dependancies)


      Make it easier to develop scripts for TRiBot


      Make it easier to use and run TRiBot


      Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.
      • 15 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...