ory-client 0.2.0.alpha27 → 0.2.0.alpha30

data/spec/api/v0alpha2_api_spec.rb

@@ -3,7 +3,7 @@
 
 #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. 
 
-The version of the OpenAPI document: v0.2.0-alpha.27
+The version of the OpenAPI document: v0.2.0-alpha.30
 Contact: support@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.1
@@ -32,44 +32,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_accept_o_auth2_consent_request
-  # Accept an OAuth 2.0 Consent Request
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject's behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\"Application my-dropbox-app wants write access to all your private files\").  The consent challenge is appended to the consent provider's URL to which the subject's user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.  This endpoint tells ORY Hydra that the subject has authorized the OAuth 2.0 client to access resources on his/her behalf. The consent provider includes additional information, such as session data for access and ID tokens, and if the consent request should be used as basis for future requests.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
-  # @param consent_challenge 
-  # @param [Hash] opts the optional parameters
-  # @option opts [AcceptOAuth2ConsentRequest] :accept_o_auth2_consent_request 
-  # @return [SuccessfulOAuth2RequestResponse]
-  describe 'admin_accept_o_auth2_consent_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_accept_o_auth2_login_request
-  # Accept an OAuth 2.0 Login Request
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory Hydra asks the login provider (sometimes called \"identity provider\") to authenticate the subject and then tell Ory Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\"show the subject a login screen\") a subject (in OAuth2 the proper name for subject is \"resource owner\").  The authentication challenge is appended to the login provider URL to which the subject's user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.  This endpoint tells ORY Hydra that the subject has successfully authenticated and includes additional information such as the subject's ID and if ORY Hydra should remember the subject's subject agent for future authentication attempts by setting a cookie.  The response contains a redirect URL which the login provider should redirect the user-agent to.
-  # @param login_challenge 
-  # @param [Hash] opts the optional parameters
-  # @option opts [AcceptOAuth2LoginRequest] :accept_o_auth2_login_request 
-  # @return [SuccessfulOAuth2RequestResponse]
-  describe 'admin_accept_o_auth2_login_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_accept_o_auth2_logout_request
-  # Accept an OAuth 2.0 Logout Request
-  # When a user or an application requests ORY Hydra to log out a user, this endpoint is used to confirm that logout request.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
-  # @param logout_challenge 
-  # @param [Hash] opts the optional parameters
-  # @return [SuccessfulOAuth2RequestResponse]
-  describe 'admin_accept_o_auth2_logout_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_create_identity
   # Create an Identity
   # This endpoint creates an identity. Learn how identities work in [Ory Kratos' User And Identity Model Documentation](https://www.ory.sh/docs/next/kratos/concepts/identity-user-model).
@@ -82,31 +44,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_create_json_web_key_set
-  # Generate a New JSON Web Key
-  # This endpoint is capable of generating JSON Web Key Sets for you. There a different strategies available, such as symmetric cryptographic keys (HS256, HS512) and asymetric cryptographic keys (RS256, ECDSA). If the specified JSON Web Key Set does not exist, it will be created.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param admin_create_json_web_key_set_body 
-  # @param [Hash] opts the optional parameters
-  # @return [JsonWebKeySet]
-  describe 'admin_create_json_web_key_set test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_create_o_auth2_client
-  # Create an OAuth 2.0 Client
-  # Create a new OAuth 2.0 client. If you pass `client_secret` the secret is used, otherwise a random secret is generated. The secret is echoed in the response. It is not possible to retrieve it later on.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param o_auth2_client 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'admin_create_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_create_self_service_recovery_link
   # Create a Recovery Link
   # This endpoint creates a recovery link which should be given to the user in order for them to recover (or activate) their account.
@@ -143,67 +80,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_delete_json_web_key
-  # Delete a JSON Web Key
-  # Use this endpoint to delete a single JSON Web Key.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param kid The JSON Web Key ID (kid)
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_delete_json_web_key test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_delete_json_web_key_set
-  # Delete a JSON Web Key Set
-  # Use this endpoint to delete a complete JSON Web Key Set and all the keys in that set.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_delete_json_web_key_set test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_delete_o_auth2_client
-  # Deletes an OAuth 2.0 Client
-  # Delete an existing OAuth 2.0 Client by its ID.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.  Make sure that this endpoint is well protected and only callable by first-party components.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_delete_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_delete_o_auth2_token
-  # Delete OAuth2 Access Tokens from a Client
-  # This endpoint deletes OAuth2 access tokens issued for a client from the database
-  # @param client_id 
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_delete_o_auth2_token test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_delete_trusted_o_auth2_jwt_grant_issuer
-  # Delete a Trusted OAuth2 JWT Bearer Grant Type Issuer
-  # Use this endpoint to delete trusted JWT Bearer Grant Type Issuer. The ID is the one returned when you created the trust relationship.  Once deleted, the associated issuer will no longer be able to perform the JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grant.
-  # @param id The id of the desired grant
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_delete_trusted_o_auth2_jwt_grant_issuer test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_extend_session
   # Calling this endpoint extends the given session ID. If `session.earliest_possible_extend` is set it will only extend the session after the specified time has passed.
   # Retrieve the session ID from the `/sessions/whoami` endpoint / `toSession` SDK method.
@@ -229,104 +105,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_get_json_web_key
-  # Fetch a JSON Web Key
-  # This endpoint returns a singular JSON Web Key. It is identified by the set and the specific key ID (kid).
-  # @param set The JSON Web Key Set
-  # @param kid The JSON Web Key ID (kid)
-  # @param [Hash] opts the optional parameters
-  # @return [JsonWebKeySet]
-  describe 'admin_get_json_web_key test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_json_web_key_set
-  # Retrieve a JSON Web Key Set
-  # This endpoint can be used to retrieve JWK Sets stored in ORY Hydra.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param [Hash] opts the optional parameters
-  # @return [JsonWebKeySet]
-  describe 'admin_get_json_web_key_set test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_o_auth2_client
-  # Get an OAuth 2.0 Client
-  # Get an OAuth 2.0 client by its ID. This endpoint never returns the client secret.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'admin_get_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_o_auth2_consent_request
-  # Get OAuth 2.0 Consent Request Information
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject's behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\"Application my-dropbox-app wants write access to all your private files\").  The consent challenge is appended to the consent provider's URL to which the subject's user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.
-  # @param consent_challenge 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2ConsentRequest]
-  describe 'admin_get_o_auth2_consent_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_o_auth2_login_request
-  # Get an OAuth 2.0 Login Request
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider (sometimes called \"identity provider\") to authenticate the subject and then tell ORY Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\"show the subject a login screen\") a subject (in OAuth2 the proper name for subject is \"resource owner\").  The authentication challenge is appended to the login provider URL to which the subject's user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.
-  # @param login_challenge 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2LoginRequest]
-  describe 'admin_get_o_auth2_login_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_o_auth2_logout_request
-  # Get an OAuth 2.0 Logout Request
-  # Use this endpoint to fetch a logout request.
-  # @param logout_challenge 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2LogoutRequest]
-  describe 'admin_get_o_auth2_logout_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_get_trusted_o_auth2_jwt_grant_issuer
-  # Get a Trusted OAuth2 JWT Bearer Grant Type Issuer
-  # Use this endpoint to get a trusted JWT Bearer Grant Type Issuer. The ID is the one returned when you created the trust relationship.
-  # @param id The id of the desired grant
-  # @param [Hash] opts the optional parameters
-  # @return [TrustedOAuth2JwtGrantIssuer]
-  describe 'admin_get_trusted_o_auth2_jwt_grant_issuer test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_introspect_o_auth2_token
-  # Introspect OAuth2 Access or Refresh Tokens
-  # The introspection endpoint allows to check if a token (both refresh and access) is active or not. An active token is neither expired nor revoked. If a token is active, additional information on the token will be included. You can set additional data for a token by setting `accessTokenExtra` during the consent flow.  For more information [read this blog post](https://www.oauth.com/oauth2-servers/token-introspection-endpoint/).
-  # @param token The string value of the token. For access tokens, this is the \\\"access_token\\\" value returned from the token endpoint defined in OAuth 2.0. For refresh tokens, this is the \\\"refresh_token\\\" value returned.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :scope An optional, space separated list of required scopes. If the access token was not granted one of the scopes, the result of active will be false.
-  # @return [IntrospectedOAuth2Token]
-  describe 'admin_introspect_o_auth2_token test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_list_identities
   # List Identities
   # Lists all identities. Does not support search at the moment.  Learn how identities work in [Ory Kratos' User And Identity Model Documentation](https://www.ory.sh/docs/next/kratos/concepts/identity-user-model).
@@ -355,51 +133,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_list_o_auth2_clients
-  # List OAuth 2.0 Clients
-  # This endpoint lists all clients in the database, and never returns client secrets. As a default it lists the first 100 clients. The `limit` parameter can be used to retrieve more clients, but it has an upper bound at 500 objects. Pagination should be used to retrieve more than 500 objects.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.  The \"Link\" header is also included in successful responses, which contains one or more links for pagination, formatted like so: '<https://project-slug.projects.oryapis.com/admin/clients?limit={limit}&offset={offset}>; rel=\"{page}\"', where page is one of the following applicable pages: 'first', 'next', 'last', and 'previous'. Multiple links can be included in this header, and will be separated by a comma.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page_size Items per page  This is the number of items per page to return. For details on pagination please head over to the [pagination documentation](https://www.ory.sh/docs/ecosystem/api-design#pagination).
-  # @option opts [String] :page_token Next Page Token  The next page token. For details on pagination please head over to the [pagination documentation](https://www.ory.sh/docs/ecosystem/api-design#pagination).
-  # @option opts [String] :client_name The name of the clients to filter by.
-  # @option opts [String] :owner The owner of the clients to filter by.
-  # @return [Array<OAuth2Client>]
-  describe 'admin_list_o_auth2_clients test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_list_o_auth2_subject_consent_sessions
-  # List OAuth 2.0 Consent Sessions of a Subject
-  # This endpoint lists all subject&#39;s granted consent sessions, including client and granted scope. If the subject is unknown or has not granted any consent sessions yet, the endpoint returns an empty JSON array with status code 200 OK.  The \&quot;Link\&quot; header is also included in successful responses, which contains one or more links for pagination, formatted like so: &#39;&lt;https://hydra-url/admin/oauth2/auth/sessions/consent?subject&#x3D;{user}&amp;limit&#x3D;{limit}&amp;offset&#x3D;{offset}&gt;; rel&#x3D;\&quot;{page}\&quot;&#39;, where page is one of the following applicable pages: &#39;first&#39;, &#39;next&#39;, &#39;last&#39;, and &#39;previous&#39;. Multiple links can be included in this header, and will be separated by a comma.
-  # @param subject The subject to list the consent sessions for.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :link The link header contains pagination links.  For details on pagination please head over to the [pagination documentation](https://www.ory.sh/docs/ecosystem/api-design#pagination).
-  # @option opts [String] :x_total_count The total number of clients.
-  # @return [Array<PreviousOAuth2ConsentSession>]
-  describe 'admin_list_o_auth2_subject_consent_sessions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_list_trusted_o_auth2_jwt_grant_issuers
-  # List Trusted OAuth2 JWT Bearer Grant Type Issuers
-  # Use this endpoint to list all trusted JWT Bearer Grant Type Issuers.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :max_items 
-  # @option opts [Integer] :default_items 
-  # @option opts [String] :issuer If optional \&quot;issuer\&quot; is supplied, only jwt-bearer grants with this issuer will be returned.
-  # @option opts [Integer] :limit The maximum amount of policies returned, upper bound is 500 policies
-  # @option opts [Integer] :offset The offset from where to start looking.
-  # @return [Array<TrustedOAuth2JwtGrantIssuer>]
-  describe 'admin_list_trusted_o_auth2_jwt_grant_issuers test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_patch_identity
   # Partially updates an Identity&#39;s field using [JSON Patch](https://jsonpatch.com/)
   # NOTE: The fields &#x60;id&#x60;, &#x60;stateChangedAt&#x60; and &#x60;credentials&#x60; are not updateable.  Learn how identities work in [Ory Kratos&#39; User And Identity Model Documentation](https://www.ory.sh/docs/next/kratos/concepts/identity-user-model).
@@ -413,96 +146,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_patch_o_auth2_client
-  # Patch an OAuth 2.0 Client
-  # Patch an existing OAuth 2.0 Client. If you pass &#x60;client_secret&#x60; the secret will be updated and returned via the API. This is the only time you will be able to retrieve the client secret, so write it down and keep it safe.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param json_patch 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'admin_patch_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_reject_o_auth2_consent_request
-  # Reject an OAuth 2.0 Consent Request
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject&#39;s behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\&quot;Application my-dropbox-app wants write access to all your private files\&quot;).  The consent challenge is appended to the consent provider&#39;s URL to which the subject&#39;s user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.  This endpoint tells ORY Hydra that the subject has not authorized the OAuth 2.0 client to access resources on his/her behalf. The consent provider must include a reason why the consent was not granted.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
-  # @param consent_challenge 
-  # @param [Hash] opts the optional parameters
-  # @option opts [RejectOAuth2Request] :reject_o_auth2_request 
-  # @return [SuccessfulOAuth2RequestResponse]
-  describe 'admin_reject_o_auth2_consent_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_reject_o_auth2_login_request
-  # Reject an OAuth 2.0 Login Request
-  # When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider (sometimes called \&quot;identity provider\&quot;) to authenticate the subject and then tell ORY Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\&quot;show the subject a login screen\&quot;) a subject (in OAuth2 the proper name for subject is \&quot;resource owner\&quot;).  The authentication challenge is appended to the login provider URL to which the subject&#39;s user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.  This endpoint tells ORY Hydra that the subject has not authenticated and includes a reason why the authentication was denied.  The response contains a redirect URL which the login provider should redirect the user-agent to.
-  # @param login_challenge 
-  # @param [Hash] opts the optional parameters
-  # @option opts [RejectOAuth2Request] :reject_o_auth2_request 
-  # @return [SuccessfulOAuth2RequestResponse]
-  describe 'admin_reject_o_auth2_login_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_reject_o_auth2_logout_request
-  # Reject an OAuth 2.0 Logout Request
-  # When a user or an application requests ORY Hydra to log out a user, this endpoint is used to deny that logout request. No body is required.  The response is empty as the logout provider has to chose what action to perform next.
-  # @param logout_challenge 
-  # @param [Hash] opts the optional parameters
-  # @option opts [RejectOAuth2Request] :reject_o_auth2_request 
-  # @return [nil]
-  describe 'admin_reject_o_auth2_logout_request test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_revoke_o_auth2_consent_sessions
-  # Revokes OAuth 2.0 Consent Sessions of a Subject for a Specific OAuth 2.0 Client
-  # This endpoint revokes a subject&#39;s granted consent sessions for a specific OAuth 2.0 Client and invalidates all associated OAuth 2.0 Access Tokens.
-  # @param subject The subject (Subject) whose consent sessions should be deleted.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :client If set, deletes only those consent sessions by the Subject that have been granted to the specified OAuth 2.0 Client ID
-  # @option opts [Boolean] :all If set to &#x60;true&#x60; deletes all consent sessions by the Subject that have been granted.
-  # @return [nil]
-  describe 'admin_revoke_o_auth2_consent_sessions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_revoke_o_auth2_login_sessions
-  # Invalidates All OAuth 2.0 Login Sessions of a Certain User
-  # This endpoint invalidates a subject&#39;s authentication session. After revoking the authentication session, the subject has to re-authenticate at ORY Hydra. This endpoint does not invalidate any tokens and does not work with OpenID Connect Front- or Back-channel logout.
-  # @param subject The subject to revoke authentication sessions for.
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'admin_revoke_o_auth2_login_sessions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_trust_o_auth2_jwt_grant_issuer
-  # Trust an OAuth2 JWT Bearer Grant Type Issuer
-  # Use this endpoint to establish a trust relationship for a JWT issuer to perform JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants [RFC7523](https://datatracker.ietf.org/doc/html/rfc7523).
-  # @param [Hash] opts the optional parameters
-  # @option opts [AdminTrustOAuth2JwtGrantIssuerBody] :admin_trust_o_auth2_jwt_grant_issuer_body 
-  # @return [TrustedOAuth2JwtGrantIssuer]
-  describe 'admin_trust_o_auth2_jwt_grant_issuer test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for admin_update_identity
   # Update an Identity
   # This endpoint updates an identity. The full identity payload (except credentials) is expected. This endpoint does not support patching.  Learn how identities work in [Ory Kratos&#39; User And Identity Model Documentation](https://www.ory.sh/docs/next/kratos/concepts/identity-user-model).
@@ -516,53 +159,26 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for admin_update_json_web_key
-  # Update a JSON Web Key
-  # Use this method if you do not want to let Hydra generate the JWKs for you, but instead save your own.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param kid The JSON Web Key ID (kid)
-  # @param [Hash] opts the optional parameters
-  # @option opts [JsonWebKey] :json_web_key 
-  # @return [JsonWebKey]
-  describe 'admin_update_json_web_key test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_update_json_web_key_set
-  # Update a JSON Web Key Set
-  # Use this method if you do not want to let Hydra generate the JWKs for you, but instead save your own.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
-  # @param set The JSON Web Key Set
-  # @param [Hash] opts the optional parameters
-  # @option opts [JsonWebKeySet] :json_web_key_set 
-  # @return [JsonWebKeySet]
-  describe 'admin_update_json_web_key_set test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for admin_update_o_auth2_client
-  # Update an OAuth 2.0 Client
-  # Update an existing OAuth 2.0 Client. If you pass &#x60;client_secret&#x60; the secret is used, otherwise a random secret is generated. The secret is echoed in the response. It is not possible to retrieve it later on.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param o_auth2_client 
+  # unit tests for create_project
+  # # Create a Project
+  # Creates a new project.
   # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'admin_update_o_auth2_client test' do
+  # @option opts [CreateProjectBody] :create_project_body 
+  # @return [Project]
+  describe 'create_project test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for create_project
-  # Create a Project
-  # Creates a new project.
+  # unit tests for create_project_api_key
+  # # Create API Token
+  # Create an API token for a project.
+  # @param project The Project ID or Project slug
   # @param [Hash] opts the optional parameters
-  # @option opts [CreateProjectBody] :create_project_body 
-  # @return [Project]
-  describe 'create_project test' do
+  # @option opts [CreateProjectApiKeyRequest] :create_project_api_key_request 
+  # @return [ProjectApiKey]
+  describe 'create_project_api_key test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -580,72 +196,14 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for discover_json_web_keys
-  # Discover JSON Web Keys
-  # This endpoint returns JSON Web Keys required to verifying OpenID Connect ID Tokens and, if enabled, OAuth 2.0 JWT Access Tokens. This endpoint can be used with client libraries like [node-jwks-rsa](https://github.com/auth0/node-jwks-rsa) among others.
-  # @param [Hash] opts the optional parameters
-  # @return [JsonWebKeySet]
-  describe 'discover_json_web_keys test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for discover_oidc_configuration
-  # OpenID Connect Discovery
-  # The well known endpoint an be used to retrieve information for OpenID Connect clients. We encourage you to not roll your own OpenID Connect client but to use an OpenID Connect client library instead. You can learn more on this flow at https://openid.net/specs/openid-connect-discovery-1_0.html .  Popular libraries for OpenID Connect clients include oidc-client-js (JavaScript), go-oidc (Golang), and others. For a full list of clients go here: https://openid.net/developers/certified/
-  # @param [Hash] opts the optional parameters
-  # @return [OidcConfiguration]
-  describe 'discover_oidc_configuration test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for dynamic_client_registration_create_o_auth2_client
-  # Register an OAuth 2.0 Client using the OpenID / OAuth2 Dynamic Client Registration Management Protocol
-  # This endpoint behaves like the administrative counterpart (&#x60;createOAuth2Client&#x60;) but is capable of facing the public internet directly and can be used in self-service. It implements the OpenID Connect Dynamic Client Registration Protocol. This feature needs to be enabled in the configuration. This endpoint is disabled by default. It can be enabled by an administrator.  Please note that using this endpoint you are not able to choose the &#x60;client_secret&#x60; nor the &#x60;client_id&#x60; as those values will be server generated when specifying &#x60;token_endpoint_auth_method&#x60; as &#x60;client_secret_basic&#x60; or &#x60;client_secret_post&#x60;.  The &#x60;client_secret&#x60; will be returned in the response and you will not be able to retrieve it later on. Write the secret down and keep it somewhere safe.
-  # @param o_auth2_client 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'dynamic_client_registration_create_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for dynamic_client_registration_delete_o_auth2_client
-  # Deletes an OAuth 2.0 Client using the OpenID / OAuth2 Dynamic Client Registration Management Protocol
-  # This endpoint behaves like the administrative counterpart (&#x60;deleteOAuth2Client&#x60;) but is capable of facing the public internet directly and can be used in self-service. It implements the OpenID Connect Dynamic Client Registration Protocol. This feature needs to be enabled in the configuration. This endpoint is disabled by default. It can be enabled by an administrator.  To use this endpoint, you will need to present the client&#39;s authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method &#x60;client_secret_post&#x60;, you need to present the client secret in the URL query. If it uses &#x60;client_secret_basic&#x60;, present the Client ID and the Client Secret in the Authorization header.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
+  # unit tests for delete_project_api_key
+  # # Delete API Token
+  # Deletes an API Token and immediately removes it.
+  # @param project The Project ID or Project slug
+  # @param token_id The Token ID
   # @param [Hash] opts the optional parameters
   # @return [nil]
-  describe 'dynamic_client_registration_delete_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for dynamic_client_registration_get_o_auth2_client
-  # Get an OAuth 2.0 Client using the OpenID / OAuth2 Dynamic Client Registration Management Protocol
-  # This endpoint behaves like the administrative counterpart (&#x60;getOAuth2Client&#x60;) but is capable of facing the public internet directly and can be used in self-service. It implements the OpenID Connect Dynamic Client Registration Protocol. This feature needs to be enabled in the configuration. This endpoint is disabled by default. It can be enabled by an administrator.  To use this endpoint, you will need to present the client&#39;s authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method &#x60;client_secret_post&#x60;, you need to present the client secret in the URL query. If it uses &#x60;client_secret_basic&#x60;, present the Client ID and the Client Secret in the Authorization header.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'dynamic_client_registration_get_o_auth2_client test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for dynamic_client_registration_update_o_auth2_client
-  # Update an OAuth 2.0 Client using the OpenID / OAuth2 Dynamic Client Registration Management Protocol
-  # This endpoint behaves like the administrative counterpart (&#x60;updateOAuth2Client&#x60;) but is capable of facing the public internet directly and can be used in self-service. It implements the OpenID Connect Dynamic Client Registration Protocol. This feature needs to be enabled in the configuration. This endpoint is disabled by default. It can be enabled by an administrator.  If you pass &#x60;client_secret&#x60; the secret is used, otherwise a random secret is generated. The secret is echoed in the response. It is not possible to retrieve it later on.  To use this endpoint, you will need to present the client&#39;s authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method &#x60;client_secret_post&#x60;, you need to present the client secret in the URL query. If it uses &#x60;client_secret_basic&#x60;, present the Client ID and the Client Secret in the Authorization header.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.
-  # @param id The id of the OAuth 2.0 Client.
-  # @param o_auth2_client 
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2Client]
-  describe 'dynamic_client_registration_update_o_auth2_client test' do
+  describe 'delete_project_api_key test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -662,19 +220,8 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for get_oidc_user_info
-  # OpenID Connect Userinfo
-  # This endpoint returns the payload of the ID Token, including the idTokenExtra values, of the provided OAuth 2.0 Access Token.  For more information please [refer to the spec](http://openid.net/specs/openid-connect-core-1_0.html#UserInfo).  In the case of authentication error, a WWW-Authenticate header might be set in the response with more information about the error. See [the spec](https://datatracker.ietf.org/doc/html/rfc6750#section-3) for more details about header format.
-  # @param [Hash] opts the optional parameters
-  # @return [OidcUserInfo]
-  describe 'get_oidc_user_info test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for get_project
-  # Get a Project
+  # # Get a Project
   # Get a projects you have access to by its ID.
   # @param project_id Project ID  The project&#39;s ID.
   # @param [Hash] opts the optional parameters
@@ -763,7 +310,7 @@ describe 'V0alpha2Api' do
   end
 
   # unit tests for get_self_service_verification_flow
-  # Get Verification Flow
+  # # Get Verification Flow
   # This endpoint returns a verification flow&#39;s context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request&#39;s HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  &#x60;&#x60;&#x60;js pseudo-code example router.get(&#39;/recovery&#39;, async function (req, res) { const flow &#x3D; await client.getSelfServiceVerificationFlow(req.header(&#39;cookie&#39;), req.query[&#39;flow&#39;])  res.render(&#39;verification&#39;, flow) })  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).
   # @param id The Flow ID  The value for this parameter comes from &#x60;request&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
   # @param [Hash] opts the optional parameters
@@ -919,8 +466,20 @@ describe 'V0alpha2Api' do
     end
   end
 
+  # unit tests for list_project_api_keys
+  # # List a Project&#39;s API Tokens
+  # A list of all the project&#39;s API tokens.
+  # @param project The Project ID or Project slug
+  # @param [Hash] opts the optional parameters
+  # @return [Array<ProjectApiKey>]
+  describe 'list_project_api_keys test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   # unit tests for list_projects
-  # List All Projects
+  # # List All Projects
   # Lists all projects you have access to.
   # @param [Hash] opts the optional parameters
   # @return [Array<ProjectMetadata>]
@@ -958,46 +517,8 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for perform_o_auth2_authorization_flow
-  # The OAuth 2.0 Authorize Endpoint
-  # This endpoint is not documented here because you should never use your own implementation to perform OAuth2 flows. OAuth2 is a very popular protocol and a library for your programming language will exists.  To learn more about this flow please refer to the specification: https://tools.ietf.org/html/rfc6749
-  # @param [Hash] opts the optional parameters
-  # @return [OAuth2ApiError]
-  describe 'perform_o_auth2_authorization_flow test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for perform_o_auth2_token_flow
-  # The OAuth 2.0 Token Endpoint
-  # The client makes a request to the token endpoint by sending the following parameters using the \&quot;application/x-www-form-urlencoded\&quot; HTTP request entity-body.  &gt; Do not implement a client for this endpoint yourself. Use a library. There are many libraries &gt; available for any programming language. You can find a list of libraries here: https://oauth.net/code/ &gt; &gt; Do note that Hydra SDK does not implement this endpoint properly. Use one of the libraries listed above
-  # @param grant_type 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :client_id 
-  # @option opts [String] :code 
-  # @option opts [String] :redirect_uri 
-  # @option opts [String] :refresh_token 
-  # @return [OAuth2TokenResponse]
-  describe 'perform_o_auth2_token_flow test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for perform_oidc_front_or_back_channel_logout
-  # OpenID Connect Front- or Back-channel Enabled Logout
-  # This endpoint initiates and completes user logout at Ory Hydra and initiates OpenID Connect Front- / Back-channel logout:  https://openid.net/specs/openid-connect-frontchannel-1_0.html https://openid.net/specs/openid-connect-backchannel-1_0.html  Back-channel logout is performed asynchronously and does not affect logout flow.
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'perform_oidc_front_or_back_channel_logout test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for purge_project
-  # Irrecoverably Purge a Project
+  # # Irrecoverably Purge a Project
   # !! Use with extreme caution !!  Using this API endpoint you can purge (completely delete) a project and its data. This action can not be undone and will delete ALL your data.  !! Use with extreme caution !!
   # @param project_id Project ID  The project&#39;s ID.
   # @param [Hash] opts the optional parameters
@@ -1021,18 +542,6 @@ describe 'V0alpha2Api' do
     end
   end
 
-  # unit tests for revoke_o_auth2_token
-  # Revoke an OAuth2 Access or Refresh Token
-  # Revoking a token (both access and refresh) means that the tokens will be invalid. A revoked access token can no longer be used to make access requests, and a revoked refresh token can no longer be used to refresh an access token. Revoking a refresh token also invalidates the access token that was created with it. A token may only be revoked by the client the token was generated for.
-  # @param token 
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'revoke_o_auth2_token test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for revoke_session
   # Calling this endpoint invalidates the specified session. The current session cannot be revoked. Session data are not deleted.
   # This endpoint is useful for:  To forcefully logout the current user from another device or session
@@ -1143,7 +652,7 @@ describe 'V0alpha2Api' do
   end
 
   # unit tests for submit_self_service_verification_flow
-  # Complete Verification Flow
+  # # Complete Verification Flow
   # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  &#x60;choose_method&#x60; expects &#x60;flow&#x60; (in the URL query) and &#x60;email&#x60; (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header &#x60;Accept: application/json&#x60; 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 &#x60;Accept&#x60; or with &#x60;Accept: text/*&#x60; it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. &#x60;sent_email&#x60; is the success state after &#x60;choose_method&#x60; when using the &#x60;link&#x60; 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 &#x60;choose_method&#x60; state. &#x60;passed_challenge&#x60; expects a &#x60;token&#x60; to be sent in the URL query and given the nature of the flow (\&quot;sending a verification link\&quot;) 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).
   # @param flow The Verification Flow ID  The value for this parameter comes from &#x60;flow&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
   # @param submit_self_service_verification_flow_body 
@@ -1171,7 +680,7 @@ describe 'V0alpha2Api' do
   end
 
   # unit tests for update_project
-  # Update an Ory Cloud Project Configuration
+  # # Update an Ory Cloud Project Configuration
   # This endpoints allows you to update the Ory Cloud Project configuration for individual services (identity, permission, ...). The configuration is fully compatible with the open source projects for the respective services (e.g. Ory Kratos for Identity, Ory Keto for Permissions).  This endpoint expects the &#x60;version&#x60; key to be set in the payload. If it is unset, it will try to import the config as if it is from the most recent version.  If you have an older version of a configuration, you should set the version key in the payload!  While this endpoint is able to process all configuration items related to features (e.g. password reset), it does not support operational configuration items (e.g. port, tracing, logging) otherwise available in the open source.  For configuration items that can not be translated to Ory Cloud, this endpoint will return a list of warnings to help you understand which parts of your config could not be processed.  Be aware that updating any service&#39;s configuration will completely override your current configuration for that service!
   # @param project_id Project ID  The project&#39;s ID.
   # @param [Hash] opts the optional parameters