1. Mixed Drink
Consuming UW web services in Drupal
Ryan Ositis (rositis@uw.edu)
Zach Griswold (zachgris@uw.edu)

2. Lots of data!
• People
• Courses
• Groups
• Academic calendar
• Lots more: http://webservices.washington.edu/
service/browse/

3. Our Focus
• People web service for directories
• Course data for website listings and
directories
• Groups data for authorization

4. Needs
• No calling into web services every time data
is needed
• Store data "the Drupal way"
• Reusable and extensible
• Secure

5. "The Drupal Way"
• No direct database code
• Reusable and extensible
• Get things done for free
Search / filtering
Versioning
Views!

6. Secure
• Sensitive data
• Must keep certificates secure
• What if Drupal / Apache was compromised?

7. Our Solution:

8. Our Solution(s):

9. Our Solution(s):
EasyCCK UW
API Courses
LTS
UW GWS UW
Auth People

10. LTS
• "Locally Trusted Service"
• Plugin-Model
• Register to handle "commands"
• Provide data to clients
• Easy to consume more data in the future
• Secure
• Manages certificates
• 1024 bit RSA + 256 bit AES

11. Did you say Daemon?

12. Why’d you do that?

13. Security. Really.

14. LTS
• Current modules / plugins
• UW People
• UW GWS Auth
• UW Courses

15. UW People
• Really 2 modules: UW People & Directory
Profile
• Pulls data from the Person Web Service (LTS)
into nodes (EasyCCK API)
• Views!

16. UW People
• Content Types
• Person
• Student
• Employee
• Simplified Profile*
• Extended Profile*

17. UW People
• Fields
• Education
• Project
• Key Work
• Recognition
• & more!

18. UW People
• Automatic
• All data is in nodes
• Views, theming layer, search, caching, etc... -
everything Drupal has to offer for nodes

19. Projects
https://drupal.ischool.uw.edu/
projects
Zach Griswold (zachgris@uw.edu)
Ryan Ositis (rositis@uw.edu)

20. Fin
Questions?
Ryan Ositis (rositis@uw.edu)
Zach Griswold (zachgris@uw.edu)