ory-client 0.0.1.alpha101 → 0.0.1.alpha103

Sign up to get free protection for your applications and to get access to all the features.
Files changed (239) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/README.md +5 -5
  4. data/docs/V0alpha2Api.md +6 -6
  5. data/lib/ory-client/api/metadata_api.rb +1 -1
  6. data/lib/ory-client/api/v0alpha0_api.rb +1 -1
  7. data/lib/ory-client/api/v0alpha2_api.rb +13 -13
  8. data/lib/ory-client/api_client.rb +1 -1
  9. data/lib/ory-client/api_error.rb +1 -1
  10. data/lib/ory-client/configuration.rb +1 -1
  11. data/lib/ory-client/models/active_project.rb +1 -1
  12. data/lib/ory-client/models/admin_create_identity_body.rb +1 -1
  13. data/lib/ory-client/models/admin_create_self_service_recovery_link_body.rb +1 -1
  14. data/lib/ory-client/models/admin_update_identity_body.rb +1 -1
  15. data/lib/ory-client/models/api_token.rb +1 -1
  16. data/lib/ory-client/models/authenticator_assurance_level.rb +1 -1
  17. data/lib/ory-client/models/cloud_account.rb +1 -1
  18. data/lib/ory-client/models/cname_settings.rb +1 -1
  19. data/lib/ory-client/models/create_custom_hostname_body.rb +1 -1
  20. data/lib/ory-client/models/create_subscription_payload.rb +1 -1
  21. data/lib/ory-client/models/error_authenticator_assurance_level_not_satisfied.rb +1 -1
  22. data/lib/ory-client/models/generic_error.rb +1 -1
  23. data/lib/ory-client/models/health_not_ready_status.rb +1 -1
  24. data/lib/ory-client/models/health_status.rb +1 -1
  25. data/lib/ory-client/models/identity.rb +1 -1
  26. data/lib/ory-client/models/identity_credentials.rb +1 -1
  27. data/lib/ory-client/models/identity_credentials_type.rb +1 -1
  28. data/lib/ory-client/models/identity_preset.rb +1 -1
  29. data/lib/ory-client/models/identity_schema.rb +1 -1
  30. data/lib/ory-client/models/identity_schema_location.rb +1 -1
  31. data/lib/ory-client/models/identity_schema_validation_result.rb +1 -1
  32. data/lib/ory-client/models/identity_state.rb +1 -1
  33. data/lib/ory-client/models/inline_object.rb +1 -1
  34. data/lib/ory-client/models/inline_response200.rb +1 -1
  35. data/lib/ory-client/models/inline_response2001.rb +1 -1
  36. data/lib/ory-client/models/inline_response503.rb +1 -1
  37. data/lib/ory-client/models/invite_payload.rb +1 -1
  38. data/lib/ory-client/models/is_owner_for_project_by_slug.rb +1 -1
  39. data/lib/ory-client/models/is_owner_for_project_by_slug_payload.rb +1 -1
  40. data/lib/ory-client/models/json_error.rb +1 -1
  41. data/lib/ory-client/models/needs_privileged_session_error.rb +1 -1
  42. data/lib/ory-client/models/null_plan.rb +1 -1
  43. data/lib/ory-client/models/pagination.rb +1 -1
  44. data/lib/ory-client/models/project.rb +1 -1
  45. data/lib/ory-client/models/project_host.rb +1 -1
  46. data/lib/ory-client/models/project_invite.rb +1 -1
  47. data/lib/ory-client/models/project_revision.rb +1 -1
  48. data/lib/ory-client/models/project_revision_hook.rb +1 -1
  49. data/lib/ory-client/models/project_revision_identity_schema.rb +1 -1
  50. data/lib/ory-client/models/project_revision_third_party_login_provider.rb +1 -1
  51. data/lib/ory-client/models/project_slug.rb +1 -1
  52. data/lib/ory-client/models/quota_project_member_seats.rb +1 -1
  53. data/lib/ory-client/models/recovery_address.rb +1 -1
  54. data/lib/ory-client/models/revoked_sessions.rb +1 -1
  55. data/lib/ory-client/models/schema_patch.rb +1 -1
  56. data/lib/ory-client/models/self_service_browser_location_change_required_error.rb +1 -1
  57. data/lib/ory-client/models/self_service_error.rb +1 -1
  58. data/lib/ory-client/models/self_service_flow_expired_error.rb +1 -1
  59. data/lib/ory-client/models/self_service_login_flow.rb +1 -1
  60. data/lib/ory-client/models/self_service_logout_url.rb +1 -1
  61. data/lib/ory-client/models/self_service_recovery_flow.rb +1 -1
  62. data/lib/ory-client/models/self_service_recovery_flow_state.rb +1 -1
  63. data/lib/ory-client/models/self_service_recovery_link.rb +1 -1
  64. data/lib/ory-client/models/self_service_registration_flow.rb +1 -1
  65. data/lib/ory-client/models/self_service_settings_flow.rb +1 -1
  66. data/lib/ory-client/models/self_service_settings_flow_state.rb +1 -1
  67. data/lib/ory-client/models/self_service_verification_flow.rb +1 -1
  68. data/lib/ory-client/models/self_service_verification_flow_state.rb +1 -1
  69. data/lib/ory-client/models/session.rb +1 -1
  70. data/lib/ory-client/models/session_authentication_method.rb +1 -1
  71. data/lib/ory-client/models/session_device.rb +1 -1
  72. data/lib/ory-client/models/settings_profile_form_config.rb +1 -1
  73. data/lib/ory-client/models/stripe_customer_response.rb +1 -1
  74. data/lib/ory-client/models/submit_self_service_login_flow_body.rb +1 -1
  75. data/lib/ory-client/models/submit_self_service_login_flow_with_lookup_secret_method_body.rb +1 -1
  76. data/lib/ory-client/models/submit_self_service_login_flow_with_oidc_method_body.rb +1 -1
  77. data/lib/ory-client/models/submit_self_service_login_flow_with_password_method_body.rb +1 -1
  78. data/lib/ory-client/models/submit_self_service_login_flow_with_totp_method_body.rb +1 -1
  79. data/lib/ory-client/models/submit_self_service_login_flow_with_web_authn_method_body.rb +1 -1
  80. data/lib/ory-client/models/submit_self_service_logout_flow_without_browser_body.rb +1 -1
  81. data/lib/ory-client/models/submit_self_service_recovery_flow_body.rb +1 -1
  82. data/lib/ory-client/models/submit_self_service_recovery_flow_with_link_method_body.rb +1 -1
  83. data/lib/ory-client/models/submit_self_service_registration_flow_body.rb +1 -1
  84. data/lib/ory-client/models/submit_self_service_registration_flow_with_oidc_method_body.rb +1 -1
  85. data/lib/ory-client/models/submit_self_service_registration_flow_with_password_method_body.rb +1 -1
  86. data/lib/ory-client/models/submit_self_service_settings_flow_body.rb +1 -1
  87. data/lib/ory-client/models/submit_self_service_settings_flow_with_lookup_method_body.rb +1 -1
  88. data/lib/ory-client/models/submit_self_service_settings_flow_with_oidc_method_body.rb +1 -1
  89. data/lib/ory-client/models/submit_self_service_settings_flow_with_password_method_body.rb +1 -1
  90. data/lib/ory-client/models/submit_self_service_settings_flow_with_profile_method_body.rb +1 -1
  91. data/lib/ory-client/models/submit_self_service_settings_flow_with_totp_method_body.rb +1 -1
  92. data/lib/ory-client/models/submit_self_service_settings_flow_with_web_authn_method_body.rb +1 -1
  93. data/lib/ory-client/models/submit_self_service_verification_flow_body.rb +1 -1
  94. data/lib/ory-client/models/submit_self_service_verification_flow_with_link_method_body.rb +1 -1
  95. data/lib/ory-client/models/subscription.rb +1 -1
  96. data/lib/ory-client/models/successful_project_config_update.rb +1 -1
  97. data/lib/ory-client/models/successful_self_service_login_without_browser.rb +1 -1
  98. data/lib/ory-client/models/successful_self_service_registration_without_browser.rb +1 -1
  99. data/lib/ory-client/models/ui_container.rb +1 -1
  100. data/lib/ory-client/models/ui_node.rb +1 -1
  101. data/lib/ory-client/models/ui_node_anchor_attributes.rb +1 -1
  102. data/lib/ory-client/models/ui_node_attributes.rb +1 -1
  103. data/lib/ory-client/models/ui_node_image_attributes.rb +1 -1
  104. data/lib/ory-client/models/ui_node_input_attributes.rb +1 -1
  105. data/lib/ory-client/models/ui_node_meta.rb +1 -1
  106. data/lib/ory-client/models/ui_node_script_attributes.rb +1 -1
  107. data/lib/ory-client/models/ui_node_text_attributes.rb +1 -1
  108. data/lib/ory-client/models/ui_text.rb +1 -1
  109. data/lib/ory-client/models/update_custom_hostname_body.rb +1 -1
  110. data/lib/ory-client/models/update_project_config_config.rb +1 -1
  111. data/lib/ory-client/models/update_subscription_payload.rb +1 -1
  112. data/lib/ory-client/models/verifiable_identity_address.rb +1 -1
  113. data/lib/ory-client/models/version.rb +1 -1
  114. data/lib/ory-client/models/warning.rb +1 -1
  115. data/lib/ory-client/version.rb +2 -2
  116. data/lib/ory-client.rb +1 -1
  117. data/ory-client.gemspec +1 -1
  118. data/spec/api/metadata_api_spec.rb +1 -1
  119. data/spec/api/v0alpha0_api_spec.rb +1 -1
  120. data/spec/api/v0alpha2_api_spec.rb +7 -7
  121. data/spec/api_client_spec.rb +1 -1
  122. data/spec/configuration_spec.rb +1 -1
  123. data/spec/models/active_project_spec.rb +1 -1
  124. data/spec/models/admin_create_identity_body_spec.rb +1 -1
  125. data/spec/models/admin_create_self_service_recovery_link_body_spec.rb +1 -1
  126. data/spec/models/admin_update_identity_body_spec.rb +1 -1
  127. data/spec/models/api_token_spec.rb +1 -1
  128. data/spec/models/authenticator_assurance_level_spec.rb +1 -1
  129. data/spec/models/cloud_account_spec.rb +1 -1
  130. data/spec/models/cname_settings_spec.rb +1 -1
  131. data/spec/models/create_custom_hostname_body_spec.rb +1 -1
  132. data/spec/models/create_subscription_payload_spec.rb +1 -1
  133. data/spec/models/error_authenticator_assurance_level_not_satisfied_spec.rb +1 -1
  134. data/spec/models/generic_error_spec.rb +1 -1
  135. data/spec/models/health_not_ready_status_spec.rb +1 -1
  136. data/spec/models/health_status_spec.rb +1 -1
  137. data/spec/models/identity_credentials_spec.rb +1 -1
  138. data/spec/models/identity_credentials_type_spec.rb +1 -1
  139. data/spec/models/identity_preset_spec.rb +1 -1
  140. data/spec/models/identity_schema_location_spec.rb +1 -1
  141. data/spec/models/identity_schema_spec.rb +1 -1
  142. data/spec/models/identity_schema_validation_result_spec.rb +1 -1
  143. data/spec/models/identity_spec.rb +1 -1
  144. data/spec/models/identity_state_spec.rb +1 -1
  145. data/spec/models/inline_object_spec.rb +1 -1
  146. data/spec/models/inline_response2001_spec.rb +1 -1
  147. data/spec/models/inline_response200_spec.rb +1 -1
  148. data/spec/models/inline_response503_spec.rb +1 -1
  149. data/spec/models/invite_payload_spec.rb +1 -1
  150. data/spec/models/is_owner_for_project_by_slug_payload_spec.rb +1 -1
  151. data/spec/models/is_owner_for_project_by_slug_spec.rb +1 -1
  152. data/spec/models/json_error_spec.rb +1 -1
  153. data/spec/models/needs_privileged_session_error_spec.rb +1 -1
  154. data/spec/models/null_plan_spec.rb +1 -1
  155. data/spec/models/pagination_spec.rb +1 -1
  156. data/spec/models/project_host_spec.rb +1 -1
  157. data/spec/models/project_invite_spec.rb +1 -1
  158. data/spec/models/project_revision_hook_spec.rb +1 -1
  159. data/spec/models/project_revision_identity_schema_spec.rb +1 -1
  160. data/spec/models/project_revision_spec.rb +1 -1
  161. data/spec/models/project_revision_third_party_login_provider_spec.rb +1 -1
  162. data/spec/models/project_slug_spec.rb +1 -1
  163. data/spec/models/project_spec.rb +1 -1
  164. data/spec/models/quota_project_member_seats_spec.rb +1 -1
  165. data/spec/models/recovery_address_spec.rb +1 -1
  166. data/spec/models/revoked_sessions_spec.rb +1 -1
  167. data/spec/models/schema_patch_spec.rb +1 -1
  168. data/spec/models/self_service_browser_location_change_required_error_spec.rb +1 -1
  169. data/spec/models/self_service_error_spec.rb +1 -1
  170. data/spec/models/self_service_flow_expired_error_spec.rb +1 -1
  171. data/spec/models/self_service_login_flow_spec.rb +1 -1
  172. data/spec/models/self_service_logout_url_spec.rb +1 -1
  173. data/spec/models/self_service_recovery_flow_spec.rb +1 -1
  174. data/spec/models/self_service_recovery_flow_state_spec.rb +1 -1
  175. data/spec/models/self_service_recovery_link_spec.rb +1 -1
  176. data/spec/models/self_service_registration_flow_spec.rb +1 -1
  177. data/spec/models/self_service_settings_flow_spec.rb +1 -1
  178. data/spec/models/self_service_settings_flow_state_spec.rb +1 -1
  179. data/spec/models/self_service_verification_flow_spec.rb +1 -1
  180. data/spec/models/self_service_verification_flow_state_spec.rb +1 -1
  181. data/spec/models/session_authentication_method_spec.rb +1 -1
  182. data/spec/models/session_device_spec.rb +1 -1
  183. data/spec/models/session_spec.rb +1 -1
  184. data/spec/models/settings_profile_form_config_spec.rb +1 -1
  185. data/spec/models/stripe_customer_response_spec.rb +1 -1
  186. data/spec/models/submit_self_service_login_flow_body_spec.rb +1 -1
  187. data/spec/models/submit_self_service_login_flow_with_lookup_secret_method_body_spec.rb +1 -1
  188. data/spec/models/submit_self_service_login_flow_with_oidc_method_body_spec.rb +1 -1
  189. data/spec/models/submit_self_service_login_flow_with_password_method_body_spec.rb +1 -1
  190. data/spec/models/submit_self_service_login_flow_with_totp_method_body_spec.rb +1 -1
  191. data/spec/models/submit_self_service_login_flow_with_web_authn_method_body_spec.rb +1 -1
  192. data/spec/models/submit_self_service_logout_flow_without_browser_body_spec.rb +1 -1
  193. data/spec/models/submit_self_service_recovery_flow_body_spec.rb +1 -1
  194. data/spec/models/submit_self_service_recovery_flow_with_link_method_body_spec.rb +1 -1
  195. data/spec/models/submit_self_service_registration_flow_body_spec.rb +1 -1
  196. data/spec/models/submit_self_service_registration_flow_with_oidc_method_body_spec.rb +1 -1
  197. data/spec/models/submit_self_service_registration_flow_with_password_method_body_spec.rb +1 -1
  198. data/spec/models/submit_self_service_settings_flow_body_spec.rb +1 -1
  199. data/spec/models/submit_self_service_settings_flow_with_lookup_method_body_spec.rb +1 -1
  200. data/spec/models/submit_self_service_settings_flow_with_oidc_method_body_spec.rb +1 -1
  201. data/spec/models/submit_self_service_settings_flow_with_password_method_body_spec.rb +1 -1
  202. data/spec/models/submit_self_service_settings_flow_with_profile_method_body_spec.rb +1 -1
  203. data/spec/models/submit_self_service_settings_flow_with_totp_method_body_spec.rb +1 -1
  204. data/spec/models/submit_self_service_settings_flow_with_web_authn_method_body_spec.rb +1 -1
  205. data/spec/models/submit_self_service_verification_flow_body_spec.rb +1 -1
  206. data/spec/models/submit_self_service_verification_flow_with_link_method_body_spec.rb +1 -1
  207. data/spec/models/subscription_spec.rb +1 -1
  208. data/spec/models/successful_project_config_update_spec.rb +1 -1
  209. data/spec/models/successful_self_service_login_without_browser_spec.rb +1 -1
  210. data/spec/models/successful_self_service_registration_without_browser_spec.rb +1 -1
  211. data/spec/models/ui_container_spec.rb +1 -1
  212. data/spec/models/ui_node_anchor_attributes_spec.rb +1 -1
  213. data/spec/models/ui_node_attributes_spec.rb +1 -1
  214. data/spec/models/ui_node_image_attributes_spec.rb +1 -1
  215. data/spec/models/ui_node_input_attributes_spec.rb +1 -1
  216. data/spec/models/ui_node_meta_spec.rb +1 -1
  217. data/spec/models/ui_node_script_attributes_spec.rb +1 -1
  218. data/spec/models/ui_node_spec.rb +1 -1
  219. data/spec/models/ui_node_text_attributes_spec.rb +1 -1
  220. data/spec/models/ui_text_spec.rb +1 -1
  221. data/spec/models/update_custom_hostname_body_spec.rb +1 -1
  222. data/spec/models/update_project_config_config_spec.rb +1 -1
  223. data/spec/models/update_subscription_payload_spec.rb +1 -1
  224. data/spec/models/verifiable_identity_address_spec.rb +1 -1
  225. data/spec/models/version_spec.rb +1 -1
  226. data/spec/models/warning_spec.rb +1 -1
  227. data/spec/spec_helper.rb +1 -1
  228. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/byebug-11.1.3/gem_make.out +2 -2
  229. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/ffi-1.15.5/gem_make.out +2 -2
  230. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/jaro_winkler-1.5.4/gem_make.out +2 -2
  231. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/psych-4.0.3/gem_make.out +2 -2
  232. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/stringio-3.0.1/gem_make.out +2 -2
  233. data/vendor/bundle/ruby/2.5.0/extensions/x86_64-linux/2.5.0/stringio-3.0.1/mkmf.log +1 -1
  234. data/vendor/bundle/ruby/2.5.0/gems/byebug-11.1.3/ext/byebug/Makefile +2 -2
  235. data/vendor/bundle/ruby/2.5.0/gems/ffi-1.15.5/ext/ffi_c/Makefile +2 -2
  236. data/vendor/bundle/ruby/2.5.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler/Makefile +2 -2
  237. data/vendor/bundle/ruby/2.5.0/gems/psych-4.0.3/ext/psych/Makefile +2 -2
  238. data/vendor/bundle/ruby/2.5.0/gems/stringio-3.0.1/ext/stringio/Makefile +2 -2
  239. metadata +2 -2
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: 0.0.1.alpha101
6
+ The version of the OpenAPI document: 0.0.1.alpha103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -11,5 +11,5 @@ OpenAPI Generator version: 5.4.0
11
11
  =end
12
12
 
13
13
  module OryClient
14
- VERSION = '0.0.1.alpha101'
14
+ VERSION = '0.0.1.alpha103'
15
15
  end
data/lib/ory-client.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
data/ory-client.gemspec CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
7
7
 
8
- The version of the OpenAPI document: v0.0.1-alpha.101
8
+ The version of the OpenAPI document: v0.0.1-alpha.103
9
9
  Contact: support@ory.sh
10
10
  Generated by: https://openapi-generator.tech
11
11
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -421,7 +421,7 @@ describe 'V0alpha2Api' do
421
421
 
422
422
  # unit tests for submit_self_service_login_flow
423
423
  # Submit a Login Flow
424
- # :::info This endpoint is EXPERIMENTAL and subject to potential breaking changes in the future. ::: Use this endpoint to complete a login flow. This endpoint behaves differently for API and browser flows. API flows expect `application/json` to be sent in the body and responds with HTTP 200 and a application/json body with the session token on success; HTTP 302 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. Browser flows expect a Content-Type of `application/x-www-form-urlencoded` or `application/json` to be sent in the body and respond with a HTTP 302 redirect to the post/after login URL or the `return_to` value if it was set and if the login succeeded; a HTTP 302 redirect to the login UI URL with the flow ID containing the validation errors otherwise. Browser flows with an accept header of `application/json` will not redirect but instead respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 302 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. If this endpoint is called with `Accept: application/json` in the header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_already_available`: The user is already signed in. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Login and User Registration Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-login-user-registration).
424
+ # :::info This endpoint is EXPERIMENTAL and subject to potential breaking changes in the future. ::: Use this endpoint to complete a login flow. This endpoint behaves differently for API and browser flows. API flows expect `application/json` to be sent in the body and responds with HTTP 200 and a application/json body with the session token on success; HTTP 303 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. Browser flows expect a Content-Type of `application/x-www-form-urlencoded` or `application/json` to be sent in the body and respond with a HTTP 303 redirect to the post/after login URL or the `return_to` value if it was set and if the login succeeded; a HTTP 303 redirect to the login UI URL with the flow ID containing the validation errors otherwise. Browser flows with an accept header of `application/json` will not redirect but instead respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 303 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. If this endpoint is called with `Accept: application/json` in the header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_already_available`: The user is already signed in. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Login and User Registration Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-login-user-registration).
425
425
  # @param flow The Login Flow ID The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/login?flow=abcde`).
426
426
  # @param [Hash] opts the optional parameters
427
427
  # @option opts [String] :x_session_token The Session Token of the Identity performing the settings flow.
@@ -435,7 +435,7 @@ describe 'V0alpha2Api' do
435
435
 
436
436
  # unit tests for submit_self_service_logout_flow
437
437
  # Complete Self-Service Logout
438
- # This endpoint logs out an identity in a self-service manner. If the `Accept` HTTP header is not set to `application/json`, the browser will be redirected (HTTP 302 Found) to the `return_to` parameter of the initial request or fall back to `urls.default_return_to`. If the `Accept` HTTP header is set to `application/json`, a 204 No Content response will be sent on successful logout instead. This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...). For API clients you can call the `/self-service/logout/api` URL directly with the Ory Session Token. More information can be found at [Ory Kratos User Logout Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-logout).
438
+ # This endpoint logs out an identity in a self-service manner. If the `Accept` HTTP header is not set to `application/json`, the browser will be redirected (HTTP 303 See Other) to the `return_to` parameter of the initial request or fall back to `urls.default_return_to`. If the `Accept` HTTP header is set to `application/json`, a 204 No Content response will be sent on successful logout instead. This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...). For API clients you can call the `/self-service/logout/api` URL directly with the Ory Session Token. More information can be found at [Ory Kratos User Logout Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-logout).
439
439
  # @param [Hash] opts the optional parameters
440
440
  # @option opts [String] :token A Valid Logout Token If you do not have a logout token because you only have a session cookie, call `/self-service/logout/urls` to generate a URL for this endpoint.
441
441
  # @option opts [String] :return_to The URL to return to after the logout was completed.
@@ -460,7 +460,7 @@ describe 'V0alpha2Api' do
460
460
 
461
461
  # unit tests for submit_self_service_recovery_flow
462
462
  # Complete Recovery Flow
463
- # Use this endpoint to complete a recovery flow. This endpoint behaves differently for API and browser flows and has several states: `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid. and a HTTP 302 Found redirect with a fresh recovery flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 302 Found redirect to the Recovery UI URL with the Recovery Flow ID appended. `sent_email` is the success state after `choose_method` for the `link` method and allows the user to request another recovery email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a recovery link\") does not have any API capabilities. The server responds with a HTTP 302 Found redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Recover UI URL with a new Recovery Flow ID which contains an error message that the recovery link was invalid. More information can be found at [Ory Kratos Account Recovery Documentation](../self-service/flows/account-recovery.mdx).
463
+ # Use this endpoint to complete a recovery flow. This endpoint behaves differently for API and browser flows and has several states: `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid. and a HTTP 303 See Other redirect with a fresh recovery flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Recovery UI URL with the Recovery Flow ID appended. `sent_email` is the success state after `choose_method` for the `link` method and allows the user to request another recovery email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a recovery link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Recover UI URL with a new Recovery Flow ID which contains an error message that the recovery link was invalid. More information can be found at [Ory Kratos Account Recovery Documentation](../self-service/flows/account-recovery.mdx).
464
464
  # @param flow The Recovery Flow ID The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/recovery?flow=abcde`).
465
465
  # @param [Hash] opts the optional parameters
466
466
  # @option opts [String] :token Recovery Token The recovery token which completes the recovery request. If the token is invalid (e.g. expired) an error will be shown to the end-user. This parameter is usually set in a link and not used by any direct API call.
@@ -474,7 +474,7 @@ describe 'V0alpha2Api' do
474
474
 
475
475
  # unit tests for submit_self_service_registration_flow
476
476
  # Submit a Registration Flow
477
- # Use this endpoint to complete a registration flow by sending an identity's traits and password. This endpoint behaves differently for API and browser flows. API flows expect `application/json` to be sent in the body and respond with HTTP 200 and a application/json body with the created identity success - if the session hook is configured the `session` and `session_token` will also be included; HTTP 302 redirect to a fresh registration flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. Browser flows expect a Content-Type of `application/x-www-form-urlencoded` or `application/json` to be sent in the body and respond with a HTTP 302 redirect to the post/after registration URL or the `return_to` value if it was set and if the registration succeeded; a HTTP 302 redirect to the registration UI URL with the flow ID containing the validation errors otherwise. Browser flows with an accept header of `application/json` will not redirect but instead respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 302 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. If this endpoint is called with `Accept: application/json` in the header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_already_available`: The user is already signed in. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Login and User Registration Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-login-user-registration).
477
+ # Use this endpoint to complete a registration flow by sending an identity's traits and password. This endpoint behaves differently for API and browser flows. API flows expect `application/json` to be sent in the body and respond with HTTP 200 and a application/json body with the created identity success - if the session hook is configured the `session` and `session_token` will also be included; HTTP 303 redirect to a fresh registration flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. Browser flows expect a Content-Type of `application/x-www-form-urlencoded` or `application/json` to be sent in the body and respond with a HTTP 303 redirect to the post/after registration URL or the `return_to` value if it was set and if the registration succeeded; a HTTP 303 redirect to the registration UI URL with the flow ID containing the validation errors otherwise. Browser flows with an accept header of `application/json` will not redirect but instead respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 303 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. If this endpoint is called with `Accept: application/json` in the header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_already_available`: The user is already signed in. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Login and User Registration Documentation](https://www.ory.sh/docs/next/kratos/self-service/flows/user-login-user-registration).
478
478
  # @param flow The Registration Flow ID The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/registration?flow=abcde`).
479
479
  # @param [Hash] opts the optional parameters
480
480
  # @option opts [SubmitSelfServiceRegistrationFlowBody] :submit_self_service_registration_flow_body
@@ -487,7 +487,7 @@ describe 'V0alpha2Api' do
487
487
 
488
488
  # unit tests for submit_self_service_settings_flow
489
489
  # Complete Settings Flow
490
- # Use this endpoint to complete a settings flow by sending an identity's updated password. This endpoint behaves differently for API and browser flows. API-initiated flows expect `application/json` to be sent in the body and respond with HTTP 200 and an application/json body with the session token on success; HTTP 302 redirect to a fresh settings flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. HTTP 401 when the endpoint is called without a valid session token. HTTP 403 when `selfservice.flows.settings.privileged_session_max_age` was reached or the session's AAL is too low. Implies that the user needs to re-authenticate. Browser flows without HTTP Header `Accept` or with `Accept: text/*` respond with a HTTP 302 redirect to the post/after settings URL or the `return_to` value if it was set and if the flow succeeded; a HTTP 302 redirect to the Settings UI URL with the flow ID containing the validation errors otherwise. a HTTP 302 redirect to the login endpoint when `selfservice.flows.settings.privileged_session_max_age` was reached or the session's AAL is too low. Browser flows with HTTP Header `Accept: application/json` respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 302 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 401 when the endpoint is called without a valid session cookie. HTTP 403 when the page is accessed without a session cookie or the session's AAL is too low. HTTP 400 on form validation errors. Depending on your configuration this endpoint might return a 403 error if the session has a lower Authenticator Assurance Level (AAL) than is possible for the identity. This can happen if the identity has password + webauthn credentials (which would result in AAL2) but the session has only AAL1. If this error occurs, ask the user to sign in with the second factor (happens automatically for server-side browser flows) or change the configuration. If this endpoint is called with a `Accept: application/json` HTTP header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_refresh_required`: The identity requested to change something that needs a privileged session. Redirect the identity to the login init endpoint with query parameters `?refresh=true&return_to=<the-current-browser-url>`, or initiate a refresh login flow otherwise. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `session_inactive`: No Ory Session was found - sign in a user first. `security_identity_mismatch`: The flow was interrupted with `session_refresh_required` but apparently some other identity logged in instead. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Settings & Profile Management Documentation](../self-service/flows/user-settings).
490
+ # Use this endpoint to complete a settings flow by sending an identity's updated password. This endpoint behaves differently for API and browser flows. API-initiated flows expect `application/json` to be sent in the body and respond with HTTP 200 and an application/json body with the session token on success; HTTP 303 redirect to a fresh settings flow if the original flow expired with the appropriate error messages set; HTTP 400 on form validation errors. HTTP 401 when the endpoint is called without a valid session token. HTTP 403 when `selfservice.flows.settings.privileged_session_max_age` was reached or the session's AAL is too low. Implies that the user needs to re-authenticate. Browser flows without HTTP Header `Accept` or with `Accept: text/*` respond with a HTTP 303 redirect to the post/after settings URL or the `return_to` value if it was set and if the flow succeeded; a HTTP 303 redirect to the Settings UI URL with the flow ID containing the validation errors otherwise. a HTTP 303 redirect to the login endpoint when `selfservice.flows.settings.privileged_session_max_age` was reached or the session's AAL is too low. Browser flows with HTTP Header `Accept: application/json` respond with HTTP 200 and a application/json body with the signed in identity and a `Set-Cookie` header on success; HTTP 303 redirect to a fresh login flow if the original flow expired with the appropriate error messages set; HTTP 401 when the endpoint is called without a valid session cookie. HTTP 403 when the page is accessed without a session cookie or the session's AAL is too low. HTTP 400 on form validation errors. Depending on your configuration this endpoint might return a 403 error if the session has a lower Authenticator Assurance Level (AAL) than is possible for the identity. This can happen if the identity has password + webauthn credentials (which would result in AAL2) but the session has only AAL1. If this error occurs, ask the user to sign in with the second factor (happens automatically for server-side browser flows) or change the configuration. If this endpoint is called with a `Accept: application/json` HTTP header, the response contains the flow without a redirect. In the case of an error, the `error.id` of the JSON response body can be one of: `session_refresh_required`: The identity requested to change something that needs a privileged session. Redirect the identity to the login init endpoint with query parameters `?refresh=true&return_to=<the-current-browser-url>`, or initiate a refresh login flow otherwise. `security_csrf_violation`: Unable to fetch the flow because a CSRF violation occurred. `session_inactive`: No Ory Session was found - sign in a user first. `security_identity_mismatch`: The flow was interrupted with `session_refresh_required` but apparently some other identity logged in instead. `security_identity_mismatch`: The requested `?return_to` address is not allowed to be used. Adjust this in the configuration! `browser_location_change_required`: Usually sent when an AJAX request indicates that the browser needs to open a specific URL. Most likely used in Social Sign In flows. More information can be found at [Ory Kratos User Settings & Profile Management Documentation](../self-service/flows/user-settings).
491
491
  # @param flow The Settings Flow ID The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/settings?flow=abcde`).
492
492
  # @param [Hash] opts the optional parameters
493
493
  # @option opts [String] :x_session_token The Session Token of the Identity performing the settings flow.
@@ -501,7 +501,7 @@ describe 'V0alpha2Api' do
501
501
 
502
502
  # unit tests for submit_self_service_verification_flow
503
503
  # Complete Verification Flow
504
- # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states: `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 302 Found redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 302 Found redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 302 Found redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid. More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
504
+ # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states: `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid. More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
505
505
  # @param flow The Verification Flow ID The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/verification?flow=abcde`).
506
506
  # @param [Hash] opts the optional parameters
507
507
  # @option opts [String] :token Verification Token The verification token which completes the verification request. If the token is invalid (e.g. expired) an error will be shown to the end-user. This parameter is usually set in a link and not used by any direct API call.
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers.
5
5
 
6
- The version of the OpenAPI document: v0.0.1-alpha.101
6
+ The version of the OpenAPI document: v0.0.1-alpha.103
7
7
  Contact: support@ory.sh
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.4.0