You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bain3 In the protocol that you gave us, we need to generate uuid to do the first post request. We also need a specific tpye of data, in this case the uuid and navigator id (null). It works on the first request then, for the second linked to the identification, we need the big json of data connection and it not works... We do some tests and by mistake, we send to times the big json instead of uuid json and then big json. And the identification works ! But we don't know how it works. We also don't know if it's linked to pronote but we can create a session without this request :
{
"nom": "FonctionParametres",
"session": "<session_id>", // int
"numeroOrdre": "<numero_ordre>",
"donneesSec": {
"donnees": {
"Uuid": "...",
"identifiantNav": "..."
}
}
}
and instead, send Identification two times, one with 3fa959b13967e0ef176069e01e23c8d7, and the other with the encrypted nOrdre with aes
The text was updated successfully, but these errors were encountered:
Each time you send a request, the counter increases by 2 (because you receive a numeroOrdre in the response to your request). Maybe that could be the issue?
Sorry for the comprehension but now, I remade some tests and I can explain the case : So I send the uuid = null and I DO NOT encrypt the NumeroOrdre with random bytes for iv but with all zeroes for EVERY request I've made. And it works. And have you a discord to get a siplier way to communicate or a group ?
wtf : I decided to try where I can go with the same request, I went to :
"{Erreur: true, MessageErreur: 'Vos droits sont insuffisants pour effectuer cette opération.'}"
Wow, I fint it nowhere
@bain3 In the protocol that you gave us, we need to generate uuid to do the first post request. We also need a specific tpye of data, in this case the uuid and navigator id (null). It works on the first request then, for the second linked to the identification, we need the big json of data connection and it not works... We do some tests and by mistake, we send to times the big json instead of uuid json and then big json. And the identification works ! But we don't know how it works. We also don't know if it's linked to pronote but we can create a session without this request :
{
"nom": "FonctionParametres",
"session": "<session_id>", // int
"numeroOrdre": "<numero_ordre>",
"donneesSec": {
"donnees": {
"Uuid": "...",
"identifiantNav": "..."
}
}
}
and instead, send Identification two times, one with 3fa959b13967e0ef176069e01e23c8d7, and the other with the encrypted nOrdre with aes
The text was updated successfully, but these errors were encountered: