Persistent timeouts

[MikeBishop]

My app has recently been seeing large timeouts (5s timeouts used to be sufficient, now I'm not getting answers at all) with the auth endpoint; both refresh and OAuth scraping are slow. I assume this is the WAF again. Anyone know what headers need to be sent to make the WAF happy?

[MikeBishop]

Stranger still, I have two different environments where the timeouts happen, but other environments where the same request (I think) gets a successful response. Something is different, but I can't tell what.

[hemang249]

Here is a minimal working code using axios ^0.21.1 for step 1 : Getting the auth form

Note : It would be better to wrap the code in a loop as the first attempt may or may not always succeed and may require a retry

const randomstring = require("randomstring");
const crypto = require("crypto");
const base64url = require("base64url");
const axios = require("axios").default;

const code_verifier = randomstring.generate(86);

const base64Digest = crypto
  .createHash("sha256")
  .update(code_verifier)
  .digest("base64");

let audience = "";
let client_id = "ownerapi";
let code_challenge_method = "S256";
let locale = "en";
let prompt = "login";
let redirect_uri = "https://auth.tesla.com/void/callback";
let response_type = "code";
let scope = "openid email offline_access";
let state = base64url.fromBase64(base64Digest);
let code_challenge = base64url.fromBase64(base64Digest);

axios
  .get(
    `https://auth.tesla.com/oauth2/v3/authorize?audience=${audience}&client_id=${client_id}&code_challenge_method=${code_challenge_method}&locale=${locale}&prompt=${prompt}&redirect_uri=${redirect_uri}&response_type=${response_type}&scope=${scope}&state=${state}&code_challenge=${code_challenge}`,
    {
      headers: {},
    }
  )
  .then((res) => {
    console.log(res);
    // do other steps
  })
  .catch((err) => console.log(err));

[MikeBishop]

I found some differences in URL generation between your code and what I'm working with, and resolving those got it back to working on my desktop. (I wasn't generating locale, prompt, or audience; some things were being URL-encoded before passing to axios, whereas yours weren't.)

But the same code that works on my desktop under WSL fails on my Raspberry Pi. There must be an impact of the environment difference, but I can't figure it out. I've got the same version of Node, same version of Axios, etc.

(Incidentally, if you pass headers: {} into Axios, your UA string will be axios/(version number), so it's not the absence of User-Agent.)

[MikeBishop]

On the Pi, your code as-is never resolves the Promise; if I add a 5s timeout to the Axios call, it bails after 5 seconds.

[hemang249]

Hm.. I'm unsure about why it stops working on a PI. In my production aws / local environment I am currently using a py based script. And on both it seems to work fine. I will look more into an implementation using node js and see if I can get it to work.

Give this script a go meanwhile, if it works for you

https://github.com/enode-engineering/tesla-oauth2/blob/main/tesla.py

[MikeBishop]

I suspect that it would, but the project I'm working in is constrained to node. I appreciate your willingness to look into it -- I'm stumped at this point.