definition.yml 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. key: oauth2
  2. title: Generic OAuth2
  3. description: OAuth 2.0 is the industry-standard protocol for authorization.
  4. author: requarks.io
  5. logo: https://static.requarks.io/logo/oauth2.svg
  6. color: blue-grey darken-2
  7. website: https://oauth.net/2/
  8. isAvailable: true
  9. useForm: false
  10. props:
  11. clientId:
  12. type: String
  13. title: Client ID
  14. hint: Application Client ID
  15. order: 1
  16. clientSecret:
  17. type: String
  18. title: Client Secret
  19. hint: Application Client Secret
  20. order: 2
  21. authorizationURL:
  22. type: String
  23. title: Authorization Endpoint URL
  24. hint: Application Authorization Endpoint URL
  25. order: 3
  26. tokenURL:
  27. type: String
  28. title: Token Endpoint URL
  29. hint: Application Token Endpoint URL
  30. order: 4
  31. userInfoURL:
  32. type: String
  33. title: User Info Endpoint URL
  34. hint: User Info Endpoint URL
  35. order: 5
  36. userIdClaim:
  37. type: String
  38. title: ID Claim
  39. hint: Field containing the user ID
  40. default: id
  41. maxWidth: 500
  42. order: 6
  43. displayNameClaim:
  44. type: String
  45. title: Display Name Claim
  46. hint: Field containing user display name
  47. default: displayName
  48. maxWidth: 500
  49. order: 7
  50. emailClaim:
  51. type: String
  52. title: Email Claim
  53. hint: Field containing the user email address
  54. default: email
  55. maxWidth: 500
  56. order: 8
  57. logoutURL:
  58. type: String
  59. title: Logout URL
  60. hint: (optional) Logout URL on the OAuth2 provider where the user will be redirected to complete the logout process.
  61. order: 9
  62. scope:
  63. type: String
  64. title: Scope
  65. hint: (optional) Application Client permission scopes.
  66. order: 10
  67. useQueryStringForAccessToken:
  68. type: Boolean
  69. default: false
  70. title: Pass access token via GET query string to User Info Endpoint
  71. hint: (optional) Pass the access token in an `access_token` parameter attached to the GET query string of the User Info Endpoint URL. Otherwise the access token will be passed in the Authorization header.
  72. order: 11