auth0 - code flow and configuring spa application with custom refresh_token times


To configure your SPA application go to your Auth0 dashbaord -> Create Application -> Provide a name ->  Choose technology -> select React

Ensure you have configure - "Allowed callback url" - for me - I have set it to https://localhost:3000 which Auth0 validation check does not approves although it does allow me to save, for now.

Ensure Refresh Token Rotation is configured - as shown below:


Next, we will use postman to get a refresh token 


Ensure you have configure 

- client id
- client secret
- grant type - code 
- auth endpoint - https://your-domain.auth0.com/authorize
- token endpoint - https://your-domain.auth0.com/oauth/token
- scope - offline_access


When you hit "Get new access token" - your token will get a refresh token on top of access_token - as shown below: 



You can see postman enable the refresh command for you - so you can trigger refresh token anytime




How do you configure a custom expiry_in token time? 

Unfortunately this is going to be a global settings - which impact all clients (spa/regular web app).

Goto Settings-> API Authorization Settings -> Default Audience (please change this into your API identifier).  Please refer to the diagram here for more information.








Comments

Post a Comment

Popular posts from this blog

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more

android studio kotlin source is null error

Image
This org.jetbrains.kotlin.util.FileAnalysisException with a java.lang.IllegalArgumentException: source must not be null is a known issue that can sometimes occur with the Kotlin compiler. It seems to be related to how the compiler analyzes certain source code structures. When this happens, you need to go clean your project and do another rebuild.  For my case, I was trying to test out the databinding = true feature. 
Read more

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more