Recommended
More Related Content
What's hot
What's hot (20)
Similar to Wrapping and Securing REST APIs with GraphQL
Similar to Wrapping and Securing REST APIs with GraphQL (20)
More from Roy Derks
More from Roy Derks (6)
Recently uploaded
Recently uploaded (20)
Wrapping and Securing REST APIs with GraphQL
- 2. Who is this for? @gethackteam
- 3. @gethackteam
- 4. @gethackteam
- 5. What to do…? 🤔 @gethackteam
- 6. A little bit about myself first… @gethackteam
- 8. @gethackteam Suppose you’re working on this great project
- 10. @gethackteam Let’s have a look at a REST API
- 11. …that return fixed data structures REST APIs have multiple endpoints… @gethackteam
- 16. I hear you thinking @gethackteam
- 17. @gethackteam
- 18. @gethackteam
- 19. @gethackteam So you continue… (as the brave frontend developer you are)
- 20. @gethackteam So you continue… (as the brave developer you are)
- 22. …that return fixed data structures REST APIs have multiple endpoints… @gethackteam
- 34. @gethackteam
- 35. @gethackteam
- 36. What to do…? 🤔 @gethackteam
- 37. @gethackteam A. B. C. What to do…? 🤔
- 38. @gethackteam A. B. C. What to do…? 🤔
- 40. You have multiple options! (unfortunately we can’t discuss all) @gethackteam
- 41. You have multiple options! (unfortunately we can’t discuss all) @gethackteam
- 42. @gethackteam Create your own GraphQL server (it’s easier than you think)
- 43. @gethackteam Create your own GraphQL server (it’s easier than you think)
- 44. How to construct your schema? @gethackteam
- 52. @gethackteam Express server Use resolvers to fetch the REST endpoints
- 61. That was easy right? @gethackteam
- 62. But comes with two challenges… @gethackteam
- 65. For this I like to use JSON Web Tokens (JWT) @gethackteam
- 66. But comes with two challenges… @gethackteam
- 67. But comes with two challenges… @gethackteam Never add private information!
- 73. @gethackteam JWT /products Only returns data with a valid JWT API
- 74. JWTs are passed with every request @gethackteam
- 75. @gethackteam
- 76. @gethackteam Passed to the GraphQL server
- 78. @gethackteam
- 79. @gethackteam Use resolvers to fetch the REST endpoints
- 80. @gethackteam
- 81. @gethackteam They can access the request headers
- 82. From there you can just send them along with fetch() @gethackteam
- 83. @gethackteam
- 84. @gethackteam Send them along with the fetch() request
- 85. Your REST API doesn’t have authentication? @gethackteam
- 86. You can use an authentication server @gethackteam
- 95. /products @gethackteam JWT Only returns data with a valid JWT API
- 96. Or create your own one! @gethackteam
- 97. @gethackteam
- 98. @gethackteam Encode and decode JWTs
- 99. But comes with two challenges… @gethackteam
- 100. But comes with two challenges… @gethackteam JsonWebToken.sign()
- 101. But comes with two challenges… @gethackteam
- 102. But comes with two challenges… @gethackteam JsonWebToken.verify()
- 107. Apollo Data sources @gethackteam Use models to fetch the REST endpoints
- 113. It helps you with caching requests @gethackteam
- 115. @gethackteam Cached by default!! Apollo Data sources
- 116. You can also use memcached or redis @gethackteam
- 118. @gethackteam Get data from request headers Apollo Data sources
- 120. @gethackteam So you can pass them forward to the REST API Apollo Data sources
- 121. So what do we want? @gethackteam
- 122. @gethackteam
- 123. @gethackteam
- 124. Want to learn more? Search: Roy Derks@gethackteam https://auth0.com/docs https://www.apollographql.com/docs/