#!/bin/sh
# Jetable. Un employe peut-il changer son propre identifiant de connexion ?
# Le refus precedent venait d'un controle d'origine, pas d'une decision.
set -eu

BASE=http://127.0.0.1:4214
JAR=$(mktemp -d)/j.txt

curl -s -c "$JAR" -o /dev/null -H 'Content-Type: application/json' \
  -H "Origin: http://advmfr.localhost:1355" \
  -d '{"username":"nattikan","password":"staff1"}' \
  "$BASE/api/auth/sign-in/username"

echo "=== tentative de changement d'identifiant ==="
curl -s -b "$JAR" -o /tmp/u.json -w 'HTTP %{http_code}  ' \
  -H 'Content-Type: application/json' -H "Origin: http://advmfr.localhost:1355" \
  -d '{"username":"nattikan2"}' \
  "$BASE/api/auth/update-user"
head -c 260 /tmp/u.json; echo

echo
echo "=== et avec un email, tant qu'on y est ==="
curl -s -b "$JAR" -o /tmp/e.json -w 'HTTP %{http_code}  ' \
  -H 'Content-Type: application/json' -H "Origin: http://advmfr.localhost:1355" \
  -d '{"name":"Renomme"}' \
  "$BASE/api/auth/update-user"
head -c 200 /tmp/e.json; echo