Skip to content

Stop auto-activating HubEE subscriptions, use the datapass scope - #309

Open
Un3x wants to merge 4 commits into
developfrom
feature/api-7125-fqf-retirer-lactivation-auto-des-abonnements-hubee-et-le
Open

Stop auto-activating HubEE subscriptions, use the datapass scope#309
Un3x wants to merge 4 commits into
developfrom
feature/api-7125-fqf-retirer-lactivation-auto-des-abonnements-hubee-et-le

Conversation

@Un3x

@Un3x Un3x commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

The DataPass webhook now only creates HubEE subscriptions (status Inactif) with a datapass-scoped token; activation and editor delegation become manual steps for the services instructeurs.

Companion PR: etalab/formulaire-qf#367

Closes API-7125 → https://linear.app/pole-api/issue/API-7125/fqf-retirer-lactivation-auto-des-abonnements-hubee-et-le-scope-admin

@linear

linear Bot commented Jul 28, 2026

Copy link
Copy Markdown

API-7125

@skelz0r skelz0r left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Le code est OK.
Par contre, comment est notifié l'équipe HubEE in-fine ? Il sont développer un système automatique ou on doit le faire ?

@damienlethiec damienlethiec left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Un commentaire mais sinon looks good to me

Comment thread site/app/clients/hubee_api_authentication.rb Outdated
Un3x added 4 commits July 29, 2026 17:19
Subscription provisioning only needs to create subscriptions; admin
rights were granted solely to allow auto-activation, which is going away.
Activation becomes a manual step for the services instructeurs, like
every other OSL; FQF volume is low enough that automation isn't worth
holding admin-level credentials.
delegationActor was only sent through the activation request; with
activation now manual, the instructeur configures the delegation in
HubEE and the INSEE lookup for the editor organization is dead weight.
find_or_create_inactive_subscription was only a seam for bolting
activation on top; the shared fixtures also claimed subscriptions come
back Actif, a state this app can no longer produce.
@Un3x
Un3x force-pushed the feature/api-7125-fqf-retirer-lactivation-auto-des-abonnements-hubee-et-le branch from ef7e315 to 7bc729a Compare July 29, 2026 15:19
@Un3x

Un3x commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Le code est OK.
Par contre, comment est notifié l'équipe HubEE in-fine ? Il sont développer un système automatique ou on doit le faire ?

Pour le moment le process est à définir.
Normalement c'est systématiquement miryad qui valide les datapass dans le cadre de la proactivité et de FQF donc de toute facon on a un point d'entré unique, donc je dirais à la mano.

Après, plein de solution possible et envisageable mais elles sont à définir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants