ory-kratos-client 0.9.0.alpha2 → 0.9.0.alpha3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0625f2c166f80ec5650907544192ad17dc5e25c0bbf8ad81705b4d5df8a6639a
-  data.tar.gz: cf20af8a9e6d01ee2c1d05fcbb176701dffe0696c08e55a56046524c3f8c1121
+  metadata.gz: 80004bea374963a3b0f63224f7a0122f9d6e29ba6b03dfead7100857c636f919
+  data.tar.gz: 12440b65478309923ca86c06590f8998780a9083212a428393b374a2ec746126
 SHA512:
-  metadata.gz: b056c5129f704dc2158ec84ec775b0eb67a5bb6f814fa68eaf1728dd798f181f0e9fe5063781ac2d3565ceb65fdd0598c11db6d47d84f1682c6d81fe619f6385
-  data.tar.gz: 4f4c4eb1b67cf61ea02b961f1947bff87007a91cce082d0295c4a478d12b021c63b4306ca50c271db56f8b13d62a183db2db2a11efc6c9181de51be385b87359
+  metadata.gz: 3dfc7d30cd43b70dae906fb2fcb7f6bba875319e1b6243cb5490a6184170c842eded65ee5d2d4cd520333400352f084677b5a92e234ee1d27a6047746dd9b3e7
+  data.tar.gz: 384363a6d4dadb4e722036302f39acda953344bdbdbf69d793e7dd27d564a767b5fc86ec6860d6c4c778ce3ac7b28a48a89284ac3c42a9ba14651fc6ef8698d7

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ory-kratos-client (0.9.0.alpha2)
+    ory-kratos-client (0.9.0.alpha3)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/README.md

@@ -11,8 +11,8 @@ technology capable of authorizing incoming requests.
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: v0.9.0-alpha.2
-- Package version: v0.9.0-alpha.2
+- API version: v0.9.0-alpha.3
+- Package version: v0.9.0-alpha.3
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -28,16 +28,16 @@ gem build ory-kratos-client.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./ory-kratos-client-v0.9.0-alpha.2.gem
+gem install ./ory-kratos-client-v0.9.0-alpha.3.gem
 ```
 
-(for development, run `gem install --dev ./ory-kratos-client-v0.9.0-alpha.2.gem` to install the development dependencies)
+(for development, run `gem install --dev ./ory-kratos-client-v0.9.0-alpha.3.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'ory-kratos-client', '~> v0.9.0-alpha.2'
+    gem 'ory-kratos-client', '~> v0.9.0-alpha.3'
 
 ### Install from Git
 

data/docs/V0alpha2Api.md

@@ -2155,7 +2155,7 @@ No authorization required
 
 Submit a Login Flow
 
-:::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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+:::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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
 
 ### Examples
 
@@ -2425,7 +2425,7 @@ No authorization required
 
 Submit a Registration Flow
 
-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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
 
 ### Examples
 

data/lib/ory-kratos-client/api/metadata_api.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/api/v0alpha2_api.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0
@@ -2032,7 +2032,7 @@ module OryKratosClient
     end
 
     # Submit a Login Flow
-    # :::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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+    # :::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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
     # @param flow [String] The Login Flow ID  The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/login?flow=abcde`).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :x_session_token The Session Token of the Identity performing the settings flow.
@@ -2044,7 +2044,7 @@ module OryKratosClient
     end
 
     # Submit a Login Flow
-    # :::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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+    # :::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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
     # @param flow [String] The Login Flow ID  The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/login?flow=abcde`).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :x_session_token The Session Token of the Identity performing the settings flow.
@@ -2311,7 +2311,7 @@ module OryKratosClient
     end
 
     # Submit a Registration Flow
-    # 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+    # 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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
     # @param flow [String] The Registration Flow ID  The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/registration?flow=abcde`).
     # @param [Hash] opts the optional parameters
     # @option opts [SubmitSelfServiceRegistrationFlowBody] :submit_self_service_registration_flow_body 
@@ -2322,7 +2322,7 @@ module OryKratosClient
     end
 
     # Submit a Registration Flow
-    # 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
+    # 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 410 if the original flow expired with the appropriate error messages set and optionally a `use_flow_id` parameter in the body; 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](https://www.ory.sh/docs/kratos/self-service/flows/user-login) and [User Registration Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration).
     # @param flow [String] The Registration Flow ID  The value for this parameter comes from `flow` URL Query parameter sent to your application (e.g. `/registration?flow=abcde`).
     # @param [Hash] opts the optional parameters
     # @option opts [SubmitSelfServiceRegistrationFlowBody] :submit_self_service_registration_flow_body 

data/lib/ory-kratos-client/api_client.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/api_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/configuration.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_body.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_import_credentials_oidc.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_import_credentials_oidc_config.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_import_credentials_oidc_provider.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_import_credentials_password.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_identity_import_credentials_password_config.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_create_self_service_recovery_link_body.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_identity_import_credentials.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/admin_update_identity_body.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/authenticator_assurance_level.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/error_authenticator_assurance_level_not_satisfied.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/generic_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/health_not_ready_status.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/health_status.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_credentials.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_credentials_oidc.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_credentials_oidc_provider.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_credentials_password.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_credentials_type.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_schema.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/identity_state.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/inline_response200.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/inline_response2001.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/inline_response503.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/json_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/needs_privileged_session_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/pagination.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/recovery_address.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/revoked_sessions.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_browser_location_change_required_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_flow_expired_error.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_login_flow.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_logout_url.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_recovery_flow.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0

data/lib/ory-kratos-client/models/self_service_recovery_flow_state.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory Kratos APIs. Public and administrative APIs are exposed on different ports. Public APIs can face the public internet without any protection while administrative APIs should never be exposed without prior authorization. To protect the administative API port you should use something like Nginx, Ory Oathkeeper, or any other technology capable of authorizing incoming requests. 
 
-The version of the OpenAPI document: v0.9.0-alpha.2
+The version of the OpenAPI document: v0.9.0-alpha.3
 Contact: hi@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.4.0