Repository navigation
Utiliser la session Bearer du Core pour le Cloud Jeedom - #88
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Utilise
repo_market::getCloudToken()pour les prévisions WeatherAPI. Le Core fournit le jeton de box et gère son renouvellement. Le Bearer est envoyé sur HTTPS avec vérification TLS.Le chemin historique reste disponible si la méthode est absente ou si aucune session Market ne fournit de jeton. Les autres erreurs de récupération du jeton remontent sans bascule vers la clé historique.
Validation locale sous PHP 8.4. Syntaxe et sélection de l’authentification vérifiées avec un jeton, sans classe ou méthode, avec une session absente, avec un jeton vide, avec un échec temporaire du Market et avec une URL HTTP.
Contrat du jeton côté Core et côté Cloud.