Scratch Auth homepage
auth

Documentation

Introduction
About
Using Scratch Auth in your website
Using a custom frontend on top of Scratch Auth
Migrating from FluffyScratch

Migrating from FluffyScratch

Note

FluffyScratch currently redirects to Scratch Auth (HTTP CODE 302). Therefore, you don't need to update your code to migrate. However, migration is still recommended to avoid extra redirects and for better stability!

Are you looking to make the switch from FluffyScratch to Scratch Auth? Good news, it's as simple as changing two lines of code!


Step 1

Change https://fluffyscratch.hampton.pw/auth/getKeys/v2?redirect=:redirectLocation to https://auth.itinerary.eu.org/auth/?redirect=:redirectLocation.

Tip: You can also add an optional name query parameter containg the name of your service. It will then show up on the login page.


Step 2

Change https://fluffyscratch.hampton.pw/auth/verify/v2/:privateCode to https://auth.itinerary.eu.org/api/auth/verifyToken?privateCode=:privateCode. Scratch Auth will return the same object as Fluffy Scratch does, with some additional keys:

JS
1{
2 valid: true || false,
3 username: '...',
4 type?: undefined || 'instant',
5 redirect: '...',
6 oneClickSignInToken?: undefined || '...',
7 instantPrivateCode?: undefined || '...'
8}