- Issue created by @drumm
- π«π·France fgm Paris, France
Since Keycloak will be hosted by a third party, doesn't that affect our GDPR profile (and equivalents like APPI, PIPA, PIPEDA...) ?
- πΊπΈUnited States hestenet Portland, OR πΊπΈ
@fgm - yes, we have a Data Processor agreement with Cloud-IAM - and will have all the appropriate disclosures updated in the privacy policy and terms as required by law. That was an important issue in selecting the vendor, and as a French company Cloud IAM felt like a better choice than some other alternatives in non-GDPR countries who 'claim' gdpr compliance.
- π«π·France fgm Paris, France
Thanks for the confirmation. And congratulations on choosing a french solution :-)
- πΊπΈUnited States hestenet Portland, OR πΊπΈ
@sanduhrs and I are talking at DrupalCon Lille Contribution Day about using the Keycloak end-point to support the localization client β .
Added a child issue: #3338978: Replace Bakery with KeyCloak SSO & social sign on β
- πΊπΈUnited States drumm NY, US
This has been moving forward. A production migration has completed in the background and we are fixing the edge cases & validating functionality. This can likely move forward in the next few weeks.
The codebases for our Keycloak extensions and migration are now available at https://gitlab.com/drupal-infrastructure/sso
- Status changed to Needs review
12 months ago 9:19pm 18 April 2024