1 / 13

Introduction to Corporate Data for CERN Drupal Sites and Planned AIS Modules

This presentation by Jan Janke (GS/AIS) discusses corporate data integration in CERN's Drupal sites and the development of AIS modules. Key highlights include the architecture of backend servers and frontend APIs that facilitate access to controlled CERN data. Emphasis is placed on secure user identification, data caching, and adherence to IT protocols. The presentation outlines future goals for module availability, monitoring usage, and expanding data access responsibly. Questions at the end encourage engagement from attendees.

wolfe
Télécharger la présentation

Introduction to Corporate Data for CERN Drupal Sites and Planned AIS Modules

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Corporate Data for CERN Drupal Sites Introduction to Planned AIS Drupal Modules ENTICE Meeting, 25.05.2011 Jan Janke (GS/AIS)

  2. AIS Module Plans EDH OHR/Foundation Roles CERN Drupal Sites CET/Qualiac SMT, APT, … "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  3. Official Interface to AIS Data • AIS controlled interface • Direct access to corporate CERN data • Public & protected data • Data gradually made available upon request "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  4. Challenge • A CERN Drupal side cannot be trusted • Currently full WebDAV access to PHP code for site admins • Secure communication between Drupal and AIS • We need to be sure that • A user requesting data really is who he/she claims to be • Data can be securely cached We actively work with IT-OIS Infrastructure Team to find solutions. Data will only be made available if a reliable identification of the end user is possible! "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  5. Architecture • Backend server • Frontend API • Customer modules Corporate Data Data Server AIS Data API Organigram Module Contact Data Module … CERN GS Department CH-1211 Genève 23 Switzerland www.cern.ch/gs-dep "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  6. Architecture: Backend Server • Processes requests • Verifies if requestor is authorised • Accesses database and returns data Corporate Data Data Server AIS Data API Organigram Module Contact Data Module … CERN GS Department CH-1211 Genève 23 Switzerland www.cern.ch/gs-dep "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  7. Architecture: Frontend API • Communicates with AIS Backend • Provides API for client modules Corporate Data Data Server AIS Data API Organigram Module Contact Data Module … CERN GS Department CH-1211 Genève 23 Switzerland www.cern.ch/gs-dep "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  8. Architecture: Customer Modules • Access data via frontend API • No direct access to AIS server • AIS provides reference implementation Corporate Data Data Server AIS Data API Organigram Module Contact Data Module … CERN GS Department CH-1211 Genève 23 Switzerland www.cern.ch/gs-dep "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  9. Data Examples • Start with publicly available data • Contact details (same data as provided by CERN Phonebook) • Organisational structure data (organigram) • Roles data • Tell me who is the Group Leader of group XYZ? "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  10. Security • Support only official IT provided Drupal infrastructure • Communication only via AIS Drupal frontend API • Reliable identification of end users • One time registration required for every site • To obtain a site specific key • All requests are validated using a signature (HMAC) "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  11. Timescale • Deal with security concerns (in progress) • Development start constrained by 1 • Build AIS reference implementation module • Comprises • Backend server • AIS Frontend API module for Drupal • Drupal modules to access organigram and contact data "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  12. Next Goals • Make first version of AIS Drupal modules available • Monitor their use • React to user specific requests • If AIS offering is accepted • Provide access to more data upon request • Allow module developers to access frontend API directly • AIS provides the data, the web developer lays it out! • Currently no plans to provide specific modules other than the reference implementation (which will be maintained). "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

  13. Thank you! • Time for questions … "Corporate Data for CERN Drupal Sites" by Jan Janke (GS-AIS-GDI)

More Related