h&''       !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~                                           Safe-Inferred"F ory-hydra-clientA Katip Log severityory-hydra-clientA Katip Log environmentory-hydra-clientA Katip logging blockory-hydra-client3Runs a Katip logging block with the Log environmentory-hydra-clientthe default log environmentory-hydra-client3Runs a Katip logging block with the Log environmentory-hydra-client3Runs a Katip logging block with the Log environmentory-hydra-client,A Katip Log environment which targets stdoutory-hydra-client3Runs a Katip logging block with the Log environment ory-hydra-client,A Katip Log environment which targets stderr ory-hydra-clientDisables Katip logging ory-hydra-clientLog a katip message ory-hydra-client're-throws exceptions after logging them  Safe-Inferred~   Safe-Inferred "/#Uory-hydra-client*A type for responses without content-body.7ory-hydra-client "*/*"8ory-hydra-client application/octet-stream9ory-hydra-client text/plain; charset=utf-8:ory-hydra-client multipart/form-data;ory-hydra-client !application/x-www-form-urlencoded<ory-hydra-client application/xml; charset=utf-8=ory-hydra-client application/json; charset=utf-8>ory-hydra-client P.Right . P.const NoContentHory-hydra-client BCL.packIory-hydra-client BL.fromStrict . T.encodeUtf8Jory-hydra-client P.idKory-hydra-client BCL.packLory-hydra-client BL.fromStrict . T.encodeUtf8Mory-hydra-client P.idNory-hydra-client WH.urlEncodeAsFormOory-hydra-client Pory-hydra-client P.Right . P.const NoContentQory-hydra-client P.Right . BCL.unpackRory-hydra-client +P.left P.show . T.decodeUtf8' . BL.toStrictSory-hydra-client P.Right . P.idTory-hydra-client P.Right . BCL.unpackUory-hydra-client P.left P.show . TL.decodeUtf8'Vory-hydra-client P.Right . P.idWory-hydra-client $P.left T.unpack . WH.urlDecodeAsFormXory-hydra-client A.eitherDecode& !"#$%&'()*+,-./102435&243/10.-+,)*'(%&#$!" 5 Safe-Inferred"%&'617]ory-hydra-clientany sequence of octets`ory-hydra-clientbase64 encoded charactersiory-hydra-client+indicates exceptions related to AuthMethodskory-hydra-client)An existential wrapper for any AuthMethodmory-hydra-client3Provides a method to apply auth methods to requestsoory-hydra-client9Determines the format of the array if type array is used.pory-hydra-client#CSV format for multiple parameters.qory-hydra-client Also called SSVrory-hydra-client Also called TSVsory-hydra-client`value1|value2|value2`tory-hydra-clientUsing multiple GET parameters, e.g. `foo=bar&foo=baz`. This is valid only for parameters in "query" ( ) or "formData" ( )uory-hydra-client Request Body{ory-hydra-clientRequest Paramsory-hydra-client/Designates the optional parameters of a requestory-hydra-client(Apply an optional parameter to a requestory-hydra-clientinfix operator / alias for addOptionalParamory-hydra-client*Designates the body parameter of a requestory-hydra-clientRepresents a request.Type Variables:req - request operationcontentType -  associated with request bodyres - response model accept -  associated with response bodyory-hydra-clientMethod of ORYHydraRequestory-hydra-clientEndpoint of ORYHydraRequestory-hydra-clientparams of ORYHydraRequestory-hydra-clienttypes of auth methodsory-hydra-clientory-hydra-clienthost supplied in the Requestory-hydra-client"user-agent supplied in the Requestory-hydra-client#Run a block using a Logger instanceory-hydra-clientConfigures the loggerory-hydra-clientList of configured auth methodsory-hydra-client3throw exceptions if auth methods are not configuredory-hydra-clientConfigures additional querystring characters which must not be URI encoded, e.g. + or :ory-hydra-client#constructs a default ORYHydraConfig configHost: http://localhostconfigUserAgent: "ory-hydra-client/0.1.0.0"ory-hydra-client2updates config use AuthMethod on matching requestsory-hydra-client(updates the config to use stdout loggingory-hydra-client(updates the config to use stderr loggingory-hydra-client%updates the config to disable loggingory-hydra-client Lensory-hydra-client Lensory-hydra-client Lensory-hydra-client Lensory-hydra-client} Lensory-hydra-client~ Lensory-hydra-client Lensory-hydra-client3apply all matching AuthMethods in config to requestory-hydra-clientRemoves Null fields. (OpenAPI-Specification 2.0 does not allow Null in JSON)ory-hydra-client$Encodes fields using WH.toQueryParamory-hydra-clientCollapse (Just "") to Nothingory-hydra-client!Collapse (Just mempty) to Nothingory-hydra-client  _parseISO8601ory-hydra-client TI.formatISO8601Millisory-hydra-client!parse an ISO8601 date-time stringory-hydra-client 2TI.parseTimeM True TI.defaultTimeLocale "%Y-%m-%d"ory-hydra-client -TI.formatTime TI.defaultTimeLocale "%Y-%m-%d"ory-hydra-clientread base64 encoded charactersory-hydra-clientshow base64 encoded charactersory-hydra-clientdisplay the configory-hydra-clientMethodory-hydra-clientEndpointory-hydra-client%req: Request Type, res: Response Type[\]_^`bacedfhgijklmnotsrqpuzyxwv{~}|{~}|uzyxwvotsrqpmnklijfhgced`ba]_^\[2 Safe-Inferred "%&89:;Bory-hydra-clientwraps an http-client Request& with request/response type parametersory-hydra-client/pair of unrender/parser error and http responseory-hydra-clientunrender/parser errorory-hydra-client http responseory-hydra-client+pair of decoded http body and http responseory-hydra-clientdecoded http bodyory-hydra-client http responseory-hydra-client.send a request returning the raw http responseory-hydra-clientsend a request returning the ory-hydra-clientlike (, but only returns the decoded http bodyory-hydra-clientlike dispatchReqLbs+, but does not validate the operation is a Producer of the "accept" 4. (Useful if the server's response is undocumented)ory-hydra-clientdispatch an InitRequestory-hydra-clientBuild an http-client Request, record from the supplied config and requestory-hydra-clientmodify the underlying Requestory-hydra-client'modify the underlying Request (monadic)ory-hydra-client0Run a block using the configured logger instanceory-hydra-clientRun a block using the configured logger instance (logs exceptions)ory-hydra-clienthttp-client Connection managerory-hydra-clientconfigory-hydra-clientrequestory-hydra-clientresponseory-hydra-clienthttp-client Connection managerory-hydra-clientconfigory-hydra-clientrequestory-hydra-clientresponseory-hydra-clienthttp-client Connection managerory-hydra-clientconfigory-hydra-clientrequestory-hydra-clientresponseory-hydra-clienthttp-client Connection managerory-hydra-clientconfigory-hydra-clientrequestory-hydra-clientresponseory-hydra-clienthttp-client Connection managerory-hydra-clientconfigory-hydra-client init requestory-hydra-clientresponseory-hydra-clientconfigory-hydra-clientrequestory-hydra-clientinitialized request Safe-Inferred"%&'689:;Oory-hydra-clientsecretory-hydra-clientusername passwordory-hydra-clientusername passwordory-hydra-clientVersionory-hydra-client-"version" - Version is the service's version.ory-hydra-clientTrustedOAuth2JwtGrantJsonWebKey OAuth2 JWT Bearer Grant Type Issuer Trusted JSON Web Keyory-hydra-client"kid" - The "key_id" is key unique identifier (same as kid header in jws/jwt).ory-hydra-client"set" - The "set" is basically a name for a group(set) of keys. Will be the same as "issuer" in grant.ory-hydra-clientTrustedOAuth2JwtGrantIssuer OAuth2 JWT Bearer Grant Type Issuer Trust Relationshipory-hydra-client"allow_any_subject" - The "allow_any_subject" indicates that the issuer is allowed to have any principal as the subject of the JWT.ory-hydra-client"created_at" - The "created_at" indicates, when grant was created.ory-hydra-client"expires_at" - The "expires_at" indicates, when grant will expire, so we will reject assertion from "issuer" targeting "subject".ory-hydra-client"id"ory-hydra-client"issuer" - The "issuer" identifies the principal that issued the JWT assertion (same as "iss" claim in JWT).ory-hydra-client "public_key"ory-hydra-client"scope" - The "scope" contains list of scope values (as described in Section 3.3 of OAuth 2.0 [RFC6749])ory-hydra-client"subject" - The "subject" identifies the principal that is the subject of the JWT.ory-hydra-clientTrustOAuth2JwtGrantIssuer Trust OAuth2 JWT Bearer Grant Type Issuer Request Bodyory-hydra-client"allow_any_subject" - The "allow_any_subject" indicates that the issuer is allowed to have any principal as the subject of the JWT.ory-hydra-clientRequired "expires_at" - The "expires_at" indicates, when grant will expire, so we will reject assertion from "issuer" targeting "subject".ory-hydra-clientRequired "issuer" - The "issuer" identifies the principal that issued the JWT assertion (same as "iss" claim in JWT).ory-hydra-clientRequired "jwk"ory-hydra-clientRequired "scope" - The "scope" contains list of scope values (as described in Section 3.3 of OAuth 2.0 [RFC6749])ory-hydra-client"subject" - The "subject" identifies the principal that is the subject of the JWT.ory-hydra-client:TokenPaginationResponseHeaders Pagination Response HeaderThe Link& HTTP header contains multiple links (first, next, last, previous) formatted as: ` https://{project-slug}.projects.oryapis.com/admin/clients?page_size={limit}&page_token={offset}; rel="{page}"` For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client"link" - The Link HTTP Header The `Link` header contains a comma-delimited list of links to the following pages: first: The first page of results. next: The next page of results. prev: The previous page of results. last: The last page of results. Pages are omitted if they do not exist. For example, if there is no next page, the `next` link is omitted. Examples: <clients?page_size=5&page_token=0>; rel="first",<clients?page_size=5&page_token=15>; rel="next",<clients?page_size=5&page_token=5>; rel="prev",<?clients?page_size=5&page_token=20>; rel="last"ory-hydra-client"x-total-count" - The X-Total-Count HTTP Header The `X-Total-Count` header contains the total number of items in the collection.ory-hydra-client?TokenPaginationRequestParameters Pagination Request ParametersThe Link& HTTP header contains multiple links (first, next, last, previous) formatted as: ` https://{project-slug}.projects.oryapis.com/admin/clients?page_size={limit}&page_token={offset}; rel="{page}"` For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client"page_size" - Items per Page This is the number of items per page to return. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client"page_token" - Next Page Token The next page token. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-clientTokenPaginationHeadersory-hydra-client"link" - The link header contains pagination links. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation . in: headerory-hydra-client:"x-total-count" - The total number of clients. in: headerory-hydra-clientTokenPaginationory-hydra-client"page_size" - Items per page This is the number of items per page to return. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client"page_token" - Next Page Token The next page token. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-clientRejectOAuth2Request The request payload used to accept a login or consent request.ory-hydra-client"error" - The error should follow the OAuth2 error format (e.g. `invalid_request`, `login_required`). Defaults to `request_denied`.ory-hydra-client"error_debug" - Debug contains information to help resolve the problem as a developer. Usually not exposed to the public but only in the server logs.ory-hydra-client"error_description" - Description of the error in a human readable format.ory-hydra-client."error_hint" - Hint to help resolve the error.ory-hydra-client"status_code" - Represents the HTTP status code of the error (e.g. 401 or 403) Defaults to 400ory-hydra-clientPaginationHeadersory-hydra-client"link" - The link header contains pagination links. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation . in: headerory-hydra-client:"x-total-count" - The total number of clients. in: headerory-hydra-client Paginationory-hydra-client"page_size" - Items per page This is the number of items per page to return. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client"page_token" - Next Page Token The next page token. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client%OidcUserInfo OpenID Connect Userinfoory-hydra-client"birthdate" - End-User's birthday, represented as an ISO 8601:2004 [ISO8601@2004] YYYY-MM-DD format. The year MAY be 0000, indicating that it is omitted. To represent only the year, YYYY format is allowed. Note that depending on the underlying platform's date related function, providing just year can result in varying month and day, so the implementers need to take this factor into account to correctly process the dates.ory-hydra-client"email" - End-User's preferred e-mail address. Its value MUST conform to the RFC 5322 [RFC5322] addr-spec syntax. The RP MUST NOT rely upon this value being unique, as discussed in Section 5.7.ory-hydra-client"email_verified" - True if the End-User's e-mail address has been verified; otherwise false. When this Claim Value is true, this means that the OP took affirmative steps to ensure that this e-mail address was controlled by the End-User at the time the verification was performed. The means by which an e-mail address is verified is context-specific, and dependent upon the trust framework or contractual agreements within which the parties are operating.ory-hydra-client"family_name" - Surname(s) or last name(s) of the End-User. Note that in some cultures, people can have multiple family names or no family name; all can be present, with the names being separated by space characters.ory-hydra-client"gender" - End-User's gender. Values defined by this specification are female and male. Other values MAY be used when neither of the defined values are applicable.ory-hydra-client"given_name" - Given name(s) or first name(s) of the End-User. Note that in some cultures, people can have multiple given names; all can be present, with the names being separated by space characters.ory-hydra-client"locale" - End-User's locale, represented as a BCP47 [RFC5646] language tag. This is typically an ISO 639-1 Alpha-2 [ISO639@1] language code in lowercase and an ISO 3166-1 Alpha-2 [ISO3166@1] country code in uppercase, separated by a dash. For example, en-US or fr-CA. As a compatibility note, some implementations have used an underscore as the separator rather than a dash, for example, en_US; Relying Parties MAY choose to accept this locale syntax as well.ory-hydra-client"middle_name" - Middle name(s) of the End-User. Note that in some cultures, people can have multiple middle names; all can be present, with the names being separated by space characters. Also note that in some cultures, middle names are not used.ory-hydra-client"name" - End-User's full name in displayable form including all name parts, possibly including titles and suffixes, ordered according to the End-User's locale and preferences.ory-hydra-client"nickname" - Casual name of the End-User that may or may not be the same as the given_name. For instance, a nickname value of Mike might be returned alongside a given_name value of Michael.ory-hydra-client"phone_number" - End-User's preferred telephone number. E.164 [E.164] is RECOMMENDED as the format of this Claim, for example, +1 (425) 555-1212 or +56 (2) 687 2400. If the phone number contains an extension, it is RECOMMENDED that the extension be represented using the RFC 3966 [RFC3966] extension syntax, for example, +1 (604) 555-1234;ext=5678.ory-hydra-client"phone_number_verified" - True if the End-User's phone number has been verified; otherwise false. When this Claim Value is true, this means that the OP took affirmative steps to ensure that this phone number was controlled by the End-User at the time the verification was performed. The means by which a phone number is verified is context-specific, and dependent upon the trust framework or contractual agreements within which the parties are operating. When true, the phone_number Claim MUST be in E.164 format and any extensions MUST be represented in RFC 3966 format.ory-hydra-client"picture" - URL of the End-User's profile picture. This URL MUST refer to an image file (for example, a PNG, JPEG, or GIF image file), rather than to a Web page containing an image. Note that this URL SHOULD specifically reference a profile photo of the End-User suitable for displaying when describing the End-User, rather than an arbitrary photo taken by the End-User.ory-hydra-client"preferred_username" - Non-unique shorthand name by which the End-User wishes to be referred to at the RP, such as janedoe or j.doe. This value MAY be any valid JSON string including special characters such as @, /, or whitespace.ory-hydra-client"profile" - URL of the End-User's profile page. The contents of this Web page SHOULD be about the End-User.ory-hydra-client?"sub" - Subject - Identifier for the End-User at the IssuerURL.ory-hydra-client"updated_at" - Time the End-User's information was last updated. Its value is a JSON number representing the number of seconds from 1970-01-01T0:0:0Z as measured in UTC until the date/time.ory-hydra-client"website" - URL of the End-User's Web page or blog. This Web page SHOULD contain information published by the End-User or an organization that the End-User is affiliated with.ory-hydra-client"zoneinfo" - String from zoneinfo [zoneinfo] time zone database representing the End-User's time zone. For example, EuropeParis or America Los_Angeles.ory-hydra-client4OidcConfiguration OpenID Connect Discovery Metadata2Includes links to several endpoints (for example `oauth2token`) and exposes information on supported signature algorithms among others.ory-hydra-clientRequired "authorization_endpoint" - OAuth 2.0 Authorization Endpoint URLory-hydra-client"backchannel_logout_session_supported" - OpenID Connect Back-Channel Logout Session Required Boolean value specifying whether the OP can pass a sid (session ID) Claim in the Logout Token to identify the RP session with the OP. If supported, the sid Claim is also included in ID Tokens issued by the OPory-hydra-client"backchannel_logout_supported" - OpenID Connect Back-Channel Logout Supported Boolean value specifying whether the OP supports back-channel logout, with true indicating support.ory-hydra-client"claims_parameter_supported" - OpenID Connect Claims Parameter Parameter Supported Boolean value specifying whether the OP supports use of the claims parameter, with true indicating support.ory-hydra-client"claims_supported" - OpenID Connect Supported Claims JSON array containing a list of the Claim Names of the Claims that the OpenID Provider MAY be able to supply values for. Note that for privacy or other reasons, this might not be an exhaustive list.ory-hydra-client"code_challenge_methods_supported" - OAuth 2.0 PKCE Supported Code Challenge Methods JSON array containing a list of Proof Key for Code Exchange (PKCE) [RFC7636] code challenge methods supported by this authorization server.ory-hydra-client"end_session_endpoint" - OpenID Connect End-Session Endpoint URL at the OP to which an RP can perform a redirect to request that the End-User be logged out at the OP.ory-hydra-client"frontchannel_logout_session_supported" - OpenID Connect Front-Channel Logout Session Required Boolean value specifying whether the OP can pass iss (issuer) and sid (session ID) query parameters to identify the RP session with the OP when the frontchannel_logout_uri is used. If supported, the sid Claim is also included in ID Tokens issued by the OP.ory-hydra-client"frontchannel_logout_supported" - OpenID Connect Front-Channel Logout Supported Boolean value specifying whether the OP supports HTTP-based logout, with true indicating support.ory-hydra-client"grant_types_supported" - OAuth 2.0 Supported Grant Types JSON array containing a list of the OAuth 2.0 Grant Type values that this OP supports.ory-hydra-clientRequired "id_token_signed_response_alg" - OpenID Connect Default ID Token Signing Algorithms Algorithm used to sign OpenID Connect ID Tokens.ory-hydra-clientRequired "id_token_signing_alg_values_supported" - OpenID Connect Supported ID Token Signing Algorithms JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for the ID Token to encode the Claims in a JWT.ory-hydra-clientRequired "issuer" - OpenID Connect Issuer URL An URL using the https scheme with no query or fragment component that the OP asserts as its IssuerURL Identifier. If IssuerURL discovery is supported , this value MUST be identical to the issuer value returned by WebFinger. This also MUST be identical to the iss Claim value in ID Tokens issued from this IssuerURL.ory-hydra-clientRequired "jwks_uri" - OpenID Connect Well-Known JSON Web Keys URL URL of the OP's JSON Web Key Set [JWK] document. This contains the signing key(s) the RP uses to validate signatures from the OP. The JWK Set MAY also contain the Server's encryption key(s), which are used by RPs to encrypt requests to the Server. When both signing and encryption keys are made available, a use (Key Use) parameter value is REQUIRED for all keys in the referenced JWK Set to indicate each key's intended usage. Although some algorithms allow the same key to be used for both signatures and encryption, doing so is NOT RECOMMENDED, as it is less secure. The JWK x5c parameter MAY be used to provide X.509 representations of keys provided. When used, the bare key values MUST still be present and MUST match those in the certificate.ory-hydra-client"registration_endpoint" - OpenID Connect Dynamic Client Registration Endpoint URLory-hydra-client"request_object_signing_alg_values_supported" - OpenID Connect Supported Request Object Signing Algorithms JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for Request Objects, which are described in Section 6.1 of OpenID Connect Core 1.0 [OpenID.Core]. These algorithms are used both when the Request Object is passed by value (using the request parameter) and when it is passed by reference (using the request_uri parameter).ory-hydra-client"request_parameter_supported" - OpenID Connect Request Parameter Supported Boolean value specifying whether the OP supports use of the request parameter, with true indicating support.ory-hydra-client"request_uri_parameter_supported" - OpenID Connect Request URI Parameter Supported Boolean value specifying whether the OP supports use of the request_uri parameter, with true indicating support.ory-hydra-client"require_request_uri_registration" - OpenID Connect Requires Request URI Registration Boolean value specifying whether the OP requires any request_uri values used to be pre-registered using the request_uris registration parameter.ory-hydra-client"response_modes_supported" - OAuth 2.0 Supported Response Modes JSON array containing a list of the OAuth 2.0 response_mode values that this OP supports.ory-hydra-clientRequired "response_types_supported" - OAuth 2.0 Supported Response Types JSON array containing a list of the OAuth 2.0 response_type values that this OP supports. Dynamic OpenID Providers MUST support the code, id_token, and the token id_token Response Type values.ory-hydra-client"revocation_endpoint" - OAuth 2.0 Token Revocation URL URL of the authorization server's OAuth 2.0 revocation endpoint.ory-hydra-client"scopes_supported" - OAuth 2.0 Supported Scope Values JSON array containing a list of the OAuth 2.0 [RFC6749] scope values that this server supports. The server MUST support the openid scope value. Servers MAY choose not to advertise some supported scope values even when this parameter is usedory-hydra-clientRequired "subject_types_supported" - OpenID Connect Supported Subject Types JSON array containing a list of the Subject Identifier types that this OP supports. Valid types include pairwise and public.ory-hydra-clientRequired0 "token_endpoint" - OAuth 2.0 Token Endpoint URLory-hydra-client"token_endpoint_auth_methods_supported" - OAuth 2.0 Supported Client Authentication Methods JSON array containing a list of Client Authentication methods supported by this Token Endpoint. The options are client_secret_post, client_secret_basic, client_secret_jwt, and private_key_jwt, as described in Section 9 of OpenID Connect Core 1.0ory-hydra-client"userinfo_endpoint" - OpenID Connect Userinfo URL URL of the OP's UserInfo Endpoint.ory-hydra-clientRequired "userinfo_signed_response_alg" - OpenID Connect User Userinfo Signing Algorithm Algorithm used to sign OpenID Connect Userinfo Responses.ory-hydra-client"userinfo_signing_alg_values_supported" - OpenID Connect Supported Userinfo Signing Algorithm JSON array containing a list of the JWS [JWS] signing algorithms (alg values) [JWA] supported by the UserInfo Endpoint to encode the Claims in a JWT [JWT].ory-hydra-client1OAuth2TokenExchange OAuth2 Token Exchange Resultory-hydra-client"access_token" - The access token issued by the authorization server.ory-hydra-client"expires_in" - The lifetime in seconds of the access token. For example, the value "3600" denotes that the access token will expire in one hour from the time the response was generated.ory-hydra-client"id_token" - To retrieve a refresh token request the id_token scope.ory-hydra-client"refresh_token" - The refresh token, which can be used to obtain new access tokens. To retrieve it add the scope "offline" to your access token request.ory-hydra-client'"scope" - The scope of the access tokenory-hydra-client+"token_type" - The type of the token issuedory-hydra-client/OAuth2RedirectTo OAuth 2.0 Redirect Browser ToContains a redirect URL used to complete a login, consent, or logout request.ory-hydra-clientRequired "redirect_to" - RedirectURL is the URL which you should redirect the user's browser to once the authentication process is completed.ory-hydra-clientOAuth2LogoutRequest Contains information about an ongoing logout request.ory-hydra-client"challenge" - Challenge is the identifier ("logout challenge") of the logout authentication request. It is used to identify the session.ory-hydra-client"client"ory-hydra-client"request_url" - RequestURL is the original Logout URL requested.ory-hydra-client"rp_initiated" - RPInitiated is set to true if the request was initiated by a Relying Party (RP), also known as an OAuth 2.0 Client.ory-hydra-client"sid" - SessionID is the login session ID that was requested to log out.ory-hydra-client"subject" - Subject is the user for whom the logout was request.ory-hydra-clientOAuth2LoginRequest Contains information on an ongoing login request.ory-hydra-clientRequired "challenge" - ID is the identifier ("login challenge") of the login request. It is used to identify the session.ory-hydra-clientRequired "client"ory-hydra-client"oidc_context"ory-hydra-clientRequired "request_url" - RequestURL is the original OAuth 2.0 Authorization URL requested by the OAuth 2.0 client. It is the URL which initiates the OAuth 2.0 Authorization Code or OAuth 2.0 Implicit flow. This URL is typically not needed, but might come in handy if you want to deal with additional request parameters.ory-hydra-clientRequired" "requested_access_token_audience"ory-hydra-clientRequired "requested_scope"ory-hydra-client"session_id" - SessionID is the login session ID. If the user-agent reuses a login session (via cookie  remember flag) this ID will remain the same. If the user-agent did not have an existing authentication session (e.g. remember is false) this will be a new random value. This value is used as the "sid" parameter in the ID Token and in OIDC Front-Back- channel logout. It's value can generally be used to associate consecutive login requests by a certain user.ory-hydra-clientRequired "skip" - Skip, if true, implies that the client has requested the same scopes from the same user previously. If true, you can skip asking the user to grant the requested scopes, and simply forward the user to the redirect URL. This feature allows you to update / set session information.ory-hydra-clientRequired "subject" - Subject is the user ID of the end-user that authenticated. Now, that end user needs to grant or deny the scope requested by the OAuth 2.0 client. If this value is set and `skip` is true, you MUST include this subject type when accepting the login request, or the request will fail.ory-hydra-clientOAuth2ConsentSessionExpiresAtory-hydra-client"access_token"ory-hydra-client"authorize_code"ory-hydra-client "id_token"ory-hydra-client "par_context"ory-hydra-client"refresh_token"ory-hydra-client/OAuth2ConsentSession OAuth 2.0 Consent Session&A completed OAuth 2.0 Consent Session.ory-hydra-client"consent_request"ory-hydra-client "expires_at"ory-hydra-client"grant_access_token_audience"ory-hydra-client "grant_scope"ory-hydra-client "handled_at"ory-hydra-client"remember" - Remember Consent Remember, if set to true, tells ORY Hydra to remember this consent authorization and reuse it if the same client asks the same user for the same, or a subset of, scope.ory-hydra-client"remember_for" - Remember Consent For RememberFor sets how long the consent authorization should be remembered for in seconds. If set to `0`, the authorization will be remembered indefinitely.ory-hydra-client "session"ory-hydra-clientOAuth2ConsentRequestOpenIDConnectContext Contains optional information about the OpenID Connect request.ory-hydra-client"acr_values" - ACRValues is the Authentication AuthorizationContext Class Reference requested in the OAuth 2.0 Authorization request. It is a parameter defined by OpenID Connect and expresses which level of authentication (e.g. 2FA) is required. OpenID Connect defines it as follows: > Requested Authentication AuthorizationContext Class Reference values. Space-separated string that specifies the acr values that the Authorization Server is being requested to use for processing this Authentication Request, with the values appearing in order of preference. The Authentication AuthorizationContext Class satisfied by the authentication performed is returned as the acr Claim Value, as specified in Section 2. The acr Claim is requested as a Voluntary Claim by this parameter.ory-hydra-client"display" - Display is a string value that specifies how the Authorization Server displays the authentication and consent user interface pages to the End-User. The defined values are: page: The Authorization Server SHOULD display the authentication and consent UI consistent with a full User Agent page view. If the display parameter is not specified, this is the default display mode. popup: The Authorization Server SHOULD display the authentication and consent UI consistent with a popup User Agent window. The popup User Agent window should be of an appropriate size for a login-focused dialog and should not obscure the entire window that it is popping up over. touch: The Authorization Server SHOULD display the authentication and consent UI consistent with a device that leverages a touch interface. wap: The Authorization Server SHOULD display the authentication and consent UI consistent with a "feature phone" type display. The Authorization Server MAY also attempt to detect the capabilities of the User Agent and present an appropriate display.ory-hydra-client"id_token_hint_claims" - IDTokenHintClaims are the claims of the ID Token previously issued by the Authorization Server being passed as a hint about the End-User's current or past authenticated session with the Client.ory-hydra-client"login_hint" - LoginHint hints about the login identifier the End-User might use to log in (if necessary). This hint can be used by an RP if it first asks the End-User for their e-mail address (or other identifier) and then wants to pass that value as a hint to the discovered authorization service. This value MAY also be a phone number in the format specified for the phone_number Claim. The use of this parameter is optional.ory-hydra-client"ui_locales" - UILocales is the End-User'id preferred languages and scripts for the user interface, represented as a space-separated list of BCP47 [RFC5646] language tag values, ordered by preference. For instance, the value "fr-CA fr en" represents a preference for French as spoken in Canada, then French (without a region designation), followed by English (without a region designation). An error SHOULD NOT result if some or all of the requested locales are not supported by the OpenID Provider.ory-hydra-clientOAuth2ConsentRequest Contains information on an ongoing consent request.ory-hydra-client"acr" - ACR represents the Authentication AuthorizationContext Class Reference value for this authentication session. You can use it to express that, for example, a user authenticated using two factor authentication.ory-hydra-client"amr"ory-hydra-clientRequired "challenge" - ID is the identifier ("authorization challenge") of the consent authorization request. It is used to identify the session.ory-hydra-client"client"ory-hydra-client "context"ory-hydra-client"login_challenge" - LoginChallenge is the login challenge this consent challenge belongs to. It can be used to associate a login and consent request in the login & consent app.ory-hydra-client"login_session_id" - LoginSessionID is the login session ID. If the user-agent reuses a login session (via cookie  remember flag) this ID will remain the same. If the user-agent did not have an existing authentication session (e.g. remember is false) this will be a new random value. This value is used as the "sid" parameter in the ID Token and in OIDC Front-Back- channel logout. It's value can generally be used to associate consecutive login requests by a certain user.ory-hydra-client"oidc_context"ory-hydra-client"request_url" - RequestURL is the original OAuth 2.0 Authorization URL requested by the OAuth 2.0 client. It is the URL which initiates the OAuth 2.0 Authorization Code or OAuth 2.0 Implicit flow. This URL is typically not needed, but might come in handy if you want to deal with additional request parameters.ory-hydra-client!"requested_access_token_audience"ory-hydra-client"requested_scope"ory-hydra-client"skip" - Skip, if true, implies that the client has requested the same scopes from the same user previously. If true, you must not ask the user to grant the requested scopes. You must however either allow or deny the consent request using the usual API call.ory-hydra-client"subject" - Subject is the user ID of the end-user that authenticated. Now, that end user needs to grant or deny the scope requested by the OAuth 2.0 client.ory-hydra-client "kid" - JSON Web Key ID The Key ID of the key to be created.ory-hydra-clientRequired "use" - JSON Web Key Use The "use" (public key use) parameter identifies the intended use of the public key. The "use" parameter is employed to indicate whether a public key is used for encrypting data or verifying the signature on data. Valid values are "enc" and "sig".ory-hydra-clientAcceptOAuth2LoginRequest HandledLoginRequest is the request payload used to accept a login request.ory-hydra-client"acr" - ACR sets the Authentication AuthorizationContext Class Reference value for this authentication session. You can use it to express that, for example, a user authenticated using two factor authentication.ory-hydra-client"amr"ory-hydra-client "context"ory-hydra-client"extend_session_lifespan" - Extend OAuth2 authentication session lifespan If set to `true`, the OAuth2 authentication cookie lifespan is extended. This is for example useful if you want the user to be able to use `prompt=none` continuously. This value can only be set to `true` if the user has an authentication, which is the case if the `skip` value is `true`.ory-hydra-client"force_subject_identifier" - ForceSubjectIdentifier forces the "pairwise" user ID of the end-user that authenticated. The "pairwise" user ID refers to the (Pairwise Identifier Algorithm)[http:/ openid.netspecsopenid-connect-core-1_0.html#PairwiseAlg] of the OpenID Connect specification. It allows you to set an obfuscated subject ("user") identifier that is unique to the client. Please note that this changes the user ID on endpoint userinfo and sub claim of the ID Token. It does not change the sub claim in the OAuth 2.0 Introspection. Per default, ORY Hydra handles this value with its own algorithm. In case you want to set this yourself you can use this field. Please note that setting this field has no effect if `pairwise` is not configured in ORY Hydra or the OAuth 2.0 Client does not expect a pairwise identifier (set via `subject_type` key in the client's configuration). Please also be aware that ORY Hydra is unable to properly compute this value during authentication. This implies that you have to compute this value on every authentication process (probably depending on the client ID or some other unique value). If you fail to compute the proper value, then authentication processes which have id_token_hint set might fail.ory-hydra-client"remember" - Remember, if set to true, tells ORY Hydra to remember this user by telling the user agent (browser) to store a cookie with authentication data. If the same user performs another OAuth 2.0 Authorization Request, he/she will not be asked to log in again.ory-hydra-client"remember_for" - RememberFor sets how long the authentication should be remembered for in seconds. If set to `0`, the authorization will be remembered for the duration of the browser session (using a session cookie).ory-hydra-clientRequired "subject" - Subject is the user ID of the end-user that authenticated.ory-hydra-clientAcceptOAuth2ConsentRequestSession Pass session data to a consent request.ory-hydra-client"access_token" - AccessToken sets session data for the access and refresh token, as well as any future tokens issued by the refresh grant. Keep in mind that this data will be available to anyone performing OAuth 2.0 Challenge Introspection. If only your services can perform OAuth 2.0 Challenge Introspection, this is usually fine. But if third parties can access that endpoint as well, sensitive data from the session might be exposed to them. Use with care!ory-hydra-client"id_token" - IDToken sets session data for the OpenID Connect ID token. Keep in mind that the session'id payloads are readable by anyone that has access to the ID Challenge. Use with care!ory-hydra-clientAcceptOAuth2ConsentRequest The request payload used to accept a consent request.ory-hydra-client"grant_access_token_audience"ory-hydra-client "grant_scope"ory-hydra-client "handled_at"ory-hydra-client"remember" - Remember, if set to true, tells ORY Hydra to remember this consent authorization and reuse it if the same client asks the same user for the same, or a subset of, scope.ory-hydra-client"remember_for" - RememberFor sets how long the consent authorization should be remembered for in seconds. If set to `0`, the authorization will be remembered indefinitely.ory-hydra-client "session"ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-clientConstruct a value of type + (by applying it's required fields, if any)ory-hydra-client(ToJSON AcceptOAuth2ConsentRequestSessionory-hydra-client*FromJSON AcceptOAuth2ConsentRequestSessionory-hydra-client!ToJSON AcceptOAuth2ConsentRequestory-hydra-client#FromJSON AcceptOAuth2ConsentRequestory-hydra-clientToJSON AcceptOAuth2LoginRequestory-hydra-client!FromJSON AcceptOAuth2LoginRequestory-hydra-clientToJSON CreateJsonWebKeySetory-hydra-clientFromJSON CreateJsonWebKeySetory-hydra-clientToJSON ErrorOAuth2ory-hydra-clientFromJSON ErrorOAuth2ory-hydra-clientToJSON GenericErrorory-hydra-clientFromJSON GenericErrorory-hydra-clientToJSON GetVersion200Responseory-hydra-clientFromJSON GetVersion200Responseory-hydra-clientToJSON HealthNotReadyStatusory-hydra-clientFromJSON HealthNotReadyStatusory-hydra-clientToJSON HealthStatusory-hydra-clientFromJSON HealthStatusory-hydra-clientToJSON IntrospectedOAuth2Tokenory-hydra-client FromJSON IntrospectedOAuth2Tokenory-hydra-clientToJSON IsReady200Responseory-hydra-clientFromJSON IsReady200Responseory-hydra-clientToJSON IsReady503Responseory-hydra-clientFromJSON IsReady503Responseory-hydra-clientToJSON JsonPatchory-hydra-clientFromJSON JsonPatchory-hydra-clientToJSON JsonWebKeyory-hydra-clientFromJSON JsonWebKeyory-hydra-clientToJSON JsonWebKeySetory-hydra-clientFromJSON JsonWebKeySetory-hydra-clientToJSON OAuth2Clientory-hydra-clientFromJSON OAuth2Clientory-hydra-client!ToJSON OAuth2ClientTokenLifespansory-hydra-client#FromJSON OAuth2ClientTokenLifespansory-hydra-client/ToJSON OAuth2ConsentRequestOpenIDConnectContextory-hydra-client1FromJSON OAuth2ConsentRequestOpenIDConnectContextory-hydra-clientToJSON OAuth2ConsentRequestory-hydra-clientFromJSON OAuth2ConsentRequestory-hydra-client$ToJSON OAuth2ConsentSessionExpiresAtory-hydra-client&FromJSON OAuth2ConsentSessionExpiresAtory-hydra-clientToJSON OAuth2ConsentSessionory-hydra-clientFromJSON OAuth2ConsentSessionory-hydra-clientToJSON OAuth2LoginRequestory-hydra-clientFromJSON OAuth2LoginRequestory-hydra-clientToJSON OAuth2LogoutRequestory-hydra-clientFromJSON OAuth2LogoutRequestory-hydra-clientToJSON OAuth2RedirectToory-hydra-clientFromJSON OAuth2RedirectToory-hydra-clientToJSON OAuth2TokenExchangeory-hydra-clientFromJSON OAuth2TokenExchangeory-hydra-clientToJSON OidcConfigurationory-hydra-clientFromJSON OidcConfigurationory-hydra-clientToJSON OidcUserInfoory-hydra-clientFromJSON OidcUserInfoory-hydra-clientToJSON Paginationory-hydra-clientFromJSON Paginationory-hydra-clientToJSON PaginationHeadersory-hydra-clientFromJSON PaginationHeadersory-hydra-clientToJSON RejectOAuth2Requestory-hydra-clientFromJSON RejectOAuth2Requestory-hydra-clientToJSON TokenPaginationory-hydra-clientFromJSON TokenPaginationory-hydra-clientToJSON TokenPaginationHeadersory-hydra-clientFromJSON TokenPaginationHeadersory-hydra-client'ToJSON TokenPaginationRequestParametersory-hydra-client)FromJSON TokenPaginationRequestParametersory-hydra-client%ToJSON TokenPaginationResponseHeadersory-hydra-client'FromJSON TokenPaginationResponseHeadersory-hydra-client ToJSON TrustOAuth2JwtGrantIssuerory-hydra-client"FromJSON TrustOAuth2JwtGrantIssuerory-hydra-client&ToJSON TrustedOAuth2JwtGrantJsonWebKeyory-hydra-client(FromJSON TrustedOAuth2JwtGrantJsonWebKeyory-hydra-client"ToJSON TrustedOAuth2JwtGrantIssuerory-hydra-client$FromJSON TrustedOAuth2JwtGrantIssuerory-hydra-clientToJSON Versionory-hydra-clientFromJSON Version ory-hydra-client<: Subject is the user ID of the end-user that authenticated.ory-hydra-client: JSON Web Key Algorithm The algorithm to be used for creating the key. Supports RS256, ES256, ES512, HS512, and HS256.ory-hydra-client7: JSON Web Key ID The Key ID of the key to be created.ory-hydra-client: JSON Web Key Use The "use" (public key use) parameter identifies the intended use of the public key. The "use" parameter is employed to indicate whether a public key is used for encrypting data or verifying the signature on data. Valid values are "enc" and "sig".ory-hydra-client%: Error message The error's message.ory-hydra-client: Active is a boolean indicator of whether or not the presented token is currently active. The specifics of a token's "active" state will vary depending on the implementation of the authorization server and the information it keeps about its tokens, but a "true" value return for the "active" property will generally indicate that a given token has been issued by this authorization server, has not been revoked by the resource owner, and is within its given time window of validity (e.g., after its issuance time and before its expiration time).ory-hydra-client: The operation to be performed. One of "add", "remove", "replace", "move", "copy", or "test".ory-hydra-client: The path to the target path. Uses JSON pointer notation. Learn more  7https://datatracker.ietf.org/doc/html/rfc6901#section-5about JSON Pointers.ory-hydra-client: The "alg" (algorithm) parameter identifies the algorithm intended for use with the key. The values used should either be registered in the IANA "JSON Web Signature and Encryption Algorithms" registry established by [JWA] or be a value that contains a Collision- Resistant Name.ory-hydra-client: The "kid" (key ID) parameter is used to match a specific key. This is used, for instance, to choose among a set of keys within a JWK Set during key rollover. The structure of the "kid" value is unspecified. When "kid" values are used within a JWK Set, different keys within the JWK Set SHOULD use distinct "kid" values. (One example in which different keys might use the same "kid" value is if they have different "kty" (key type) values but are considered to be equivalent alternatives by the application using them.) The "kid" value is a case-sensitive string.ory-hydra-client: The "kty" (key type) parameter identifies the cryptographic algorithm family used with the key, such as "RSA" or "EC". "kty" values should either be registered in the IANA "JSON Web Key Types" registry established by [JWA] or be a value that contains a Collision- Resistant Name. The "kty" value is a case-sensitive string.ory-hydra-client: Use ("public key use") identifies the intended use of the public key. The "use" parameter is employed to indicate whether a public key is used for encrypting data or verifying the signature on data. Values are commonly "sig" (signature) or "enc" (encryption).ory-hydra-client: ID is the identifier ("authorization challenge") of the consent authorization request. It is used to identify the session.ory-hydra-client: ID is the identifier ("login challenge") of the login request. It is used to identify the session.ory-hydra-client ory-hydra-client: RequestURL is the original OAuth 2.0 Authorization URL requested by the OAuth 2.0 client. It is the URL which initiates the OAuth 2.0 Authorization Code or OAuth 2.0 Implicit flow. This URL is typically not needed, but might come in handy if you want to deal with additional request parameters.ory-hydra-client ory-hydra-client ory-hydra-client: Skip, if true, implies that the client has requested the same scopes from the same user previously. If true, you can skip asking the user to grant the requested scopes, and simply forward the user to the redirect URL. This feature allows you to update / set session information.ory-hydra-client: Subject is the user ID of the end-user that authenticated. Now, that end user needs to grant or deny the scope requested by the OAuth 2.0 client. If this value is set and skip is true, you MUST include this subject type when accepting the login request, or the request will fail.ory-hydra-client: RedirectURL is the URL which you should redirect the user's browser to once the authentication process is completed. ory-hydra-client&: OAuth 2.0 Authorization Endpoint URLory-hydra-client: OpenID Connect Default ID Token Signing Algorithms Algorithm used to sign OpenID Connect ID Tokens.ory-hydra-client: OpenID Connect Supported ID Token Signing Algorithms JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for the ID Token to encode the Claims in a JWT.ory-hydra-client: OpenID Connect Issuer URL An URL using the https scheme with no query or fragment component that the OP asserts as its IssuerURL Identifier. If IssuerURL discovery is supported , this value MUST be identical to the issuer value returned by WebFinger. This also MUST be identical to the iss Claim value in ID Tokens issued from this IssuerURL.ory-hydra-client: OpenID Connect Well-Known JSON Web Keys URL URL of the OP's JSON Web Key Set [JWK] document. This contains the signing key(s) the RP uses to validate signatures from the OP. The JWK Set MAY also contain the Server's encryption key(s), which are used by RPs to encrypt requests to the Server. When both signing and encryption keys are made available, a use (Key Use) parameter value is REQUIRED for all keys in the referenced JWK Set to indicate each key's intended usage. Although some algorithms allow the same key to be used for both signatures and encryption, doing so is NOT RECOMMENDED, as it is less secure. The JWK x5c parameter MAY be used to provide X.509 representations of keys provided. When used, the bare key values MUST still be present and MUST match those in the certificate.ory-hydra-client: OAuth 2.0 Supported Response Types JSON array containing a list of the OAuth 2.0 response_type values that this OP supports. Dynamic OpenID Providers MUST support the code, id_token, and the token id_token Response Type values.ory-hydra-client: OpenID Connect Supported Subject Types JSON array containing a list of the Subject Identifier types that this OP supports. Valid types include pairwise and public.ory-hydra-client: OAuth 2.0 Token Endpoint URLory-hydra-client: OpenID Connect User Userinfo Signing Algorithm Algorithm used to sign OpenID Connect Userinfo Responses.ory-hydra-client: The "expires_at" indicates, when grant will expire, so we will reject assertion from "issuer" targeting "subject".ory-hydra-client: The "issuer" identifies the principal that issued the JWT assertion (same as "iss" claim in JWT).ory-hydra-client ory-hydra-client: The "scope" contains list of scope values (as described in Section 3.3 of OAuth 2.0 [RFC6749]) Safe-Inferred"Xory-hydra-client GET /.well-known/jwks.json!Discover Well-Known JSON Web KeysThis 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  &https://github.com/auth0/node-jwks-rsa node-jwks-rsa among others.ory-hydra-client application/json Safe-Inferred"pory-hydra-client POST /oauth2/register?Register OAuth2 Client using OpenID Dynamic Client Registration;This endpoint behaves like the administrative counterpart (createOAuth2Client) 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  client_secret nor the  client_id: as those values will be server generated when specifying token_endpoint_auth_method as client_secret_basic or client_secret_post. The  client_secret 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.ory-hydra-client DELETE /oauth2/register/{id}Delete OAuth 2.0 Client using the OpenID Dynamic Client Registration Management Protocol;This endpoint behaves like the administrative counterpart (deleteOAuth2Client) 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's authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method client_secret_post, you need to present the client secret in the URL query. If it uses client_secret_basic, 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. AuthMethod: ory-hydra-client %GET /.well-known/openid-configurationOpenID Connect DiscoveryA mechanism for an OpenID Connect Relying Party to discover the End-User's OpenID Provider and obtain information needed to interact with it, including its OAuth 2.0 endpoint locations. 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/ory-hydra-client GET /oauth2/register/{id}:Get OAuth2 Client using OpenID Dynamic Client Registration;This endpoint behaves like the administrative counterpart (getOAuth2Client) 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. To use this endpoint, you will need to present the client's authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method client_secret_post, you need to present the client secret in the URL query. If it uses client_secret_basic, present the Client ID and the Client Secret in the Authorization header. AuthMethod: ory-hydra-client  GET /userinfoOpenID Connect Userinfo=This endpoint returns the payload of the ID Token, including `session.id_token` values, of the provided OAuth 2.0 Access Token's consent request. In the case of authentication error, a WWW-Authenticate header might be set in the response with more information about the error. See  7https://datatracker.ietf.org/doc/html/rfc6750#section-3the spec& for more details about header format. AuthMethod: ory-hydra-client GET /oauth2/sessions/logout5OpenID Connect Front- and Back-channel Enabled LogoutThis endpoint initiates and completes user logout at the Ory OAuth2 & OpenID provider and initiates OpenID Connect Front-  Back-channel logout: https: openid.netspecs+openid-connect-frontchannel-1_0.html https: openid.netspecs/openid-connect-backchannel-1_0.html Back-channel logout is performed asynchronously and does not affect logout flow.ory-hydra-client PUT /oauth2/register/{id}:Set OAuth2 Client using OpenID Dynamic Client Registration;This endpoint behaves like the administrative counterpart (setOAuth2Client) but is capable of facing the public internet directly to be used by third parties. It implements the OpenID Connect Dynamic Client Registration Protocol. This feature is disabled per default. It can be enabled by a system administrator. If you pass  client_secret the secret is used, otherwise the existing secret is used. If set, 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's authentication credentials. If the OAuth2 Client uses the Token Endpoint Authentication Method client_secret_post, you need to present the client secret in the URL query. If it uses client_secret_basic, 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. AuthMethod: ory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client Body Param  OAuth2Client+ - Dynamic Client Registration Request Bodyory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client Body Param  OAuth2Client - OAuth 2.0 Client Request Bodyory-hydra-client:"oAuth2Client" - Dynamic Client Registration Request Bodyory-hydra-client'"id" - The id of the OAuth 2.0 Client.ory-hydra-client'"id" - The id of the OAuth 2.0 Client.ory-hydra-client/"oAuth2Client" - OAuth 2.0 Client Request Bodyory-hydra-client"id" - OAuth 2.0 Client ID Safe-Inferred"vory-hydra-client .PUT /admin/oauth2/auth/requests/consent/accept Accept OAuth 2.0 Consent RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell Ory now about it. If the subject authenticated, heshe 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 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 if the subject accepted or rejected the request. This endpoint tells Ory that the subject has authorized the OAuth 2.0 client to access resources on hisher 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. The default consent provider is available via the Ory Managed Account Experience. To customize the consent provider, please head over to the OAuth 2.0 documentation.ory-hydra-client ,PUT /admin/oauth2/auth/requests/login/acceptAccept OAuth 2.0 Login RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell the Ory OAuth2 Service about it. 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 that the subject has successfully authenticated and includes additional information such as the subject's ID and if Ory 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.ory-hydra-client -PUT /admin/oauth2/auth/requests/logout/accept'Accept OAuth 2.0 Session Logout RequestWhen a user or an application requests Ory OAuth 2.0 to remove the session state of a subject, 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.ory-hydra-client POST /admin/clientsCreate 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.ory-hydra-client DELETE /admin/clients/{id}Delete OAuth 2.0 ClientDelete 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.ory-hydra-client DELETE /admin/oauth2/tokens=Delete OAuth 2.0 Access Tokens from specific OAuth 2.0 ClientThis endpoint deletes OAuth2 access tokens issued to an OAuth 2.0 Client from the database.ory-hydra-client 2DELETE /admin/trust/grants/jwt-bearer/issuers/{id}2Delete Trusted OAuth2 JWT Bearer Grant Type IssuerUse 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.ory-hydra-client GET /admin/clients/{id}Get an OAuth 2.0 ClientGet 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.ory-hydra-client 'GET /admin/oauth2/auth/requests/consentGet OAuth 2.0 Consent RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell Ory 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 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 if the subject accepted or rejected the request. The default consent provider is available via the Ory Managed Account Experience. To customize the consent provider, please head over to the OAuth 2.0 documentation.ory-hydra-client %GET /admin/oauth2/auth/requests/loginGet OAuth 2.0 Login RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell the Ory OAuth2 Service about it. Per default, the login provider is Ory itself. You may use a different login provider which needs to be a 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.ory-hydra-client &GET /admin/oauth2/auth/requests/logout$Get OAuth 2.0 Session Logout Request;Use this endpoint to fetch an Ory OAuth 2.0 logout request.ory-hydra-client /GET /admin/trust/grants/jwt-bearer/issuers/{id}/Get Trusted OAuth2 JWT Bearer Grant Type IssuerUse this endpoint to get a trusted JWT Bearer Grant Type Issuer. The ID is the one returned when you created the trust relationship.ory-hydra-client POST /admin/oauth2/introspect+Introspect OAuth2 Access and Refresh TokensThe 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 `session.access_token` during the consent flow.ory-hydra-client GET /admin/clientsList OAuth 2.0 ClientsThis endpoint lists all clients in the database, and never returns client secrets. As a default it lists the first 100 clients.ory-hydra-client 'GET /admin/oauth2/auth/sessions/consent,List OAuth 2.0 Consent Sessions of a SubjectThis endpoint lists all subject'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.ory-hydra-client *GET /admin/trust/grants/jwt-bearer/issuers1List Trusted OAuth2 JWT Bearer Grant Type IssuersUse this endpoint to list all trusted JWT Bearer Grant Type Issuers.ory-hydra-client GET /oauth2/authOAuth 2.0 Authorize EndpointUse open source libraries to perform OAuth 2.0 and OpenID Connect available for any programming language. You can find a list of libraries at  https://oauth.net/code/8 The Ory SDK is not yet able to this endpoint properly.ory-hydra-client POST /oauth2/tokenThe OAuth 2.0 Token EndpointUse open source libraries to perform OAuth 2.0 and OpenID Connect available for any programming language. You can find a list of libraries here  https://oauth.net/code/8 The Ory SDK is not yet able to this endpoint properly. AuthMethod: , ory-hydra-client PATCH /admin/clients/{id}Patch OAuth 2.0 ClientPatch an existing OAuth 2.0 Client using JSON Patch. If you pass  client_secret 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.ory-hydra-client .PUT /admin/oauth2/auth/requests/consent/reject Reject OAuth 2.0 Consent RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell Ory now about it. If the subject authenticated, heshe 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 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 if the subject accepted or rejected the request. This endpoint tells Ory that the subject has not authorized the OAuth 2.0 client to access resources on hisher 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. The default consent provider is available via the Ory Managed Account Experience. To customize the consent provider, please head over to the OAuth 2.0 documentation.ory-hydra-client ,PUT /admin/oauth2/auth/requests/login/rejectReject OAuth 2.0 Login RequestWhen an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, Ory asks the login provider to authenticate the subject and then tell the Ory OAuth2 Service about it. 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 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.ory-hydra-client -PUT /admin/oauth2/auth/requests/logout/reject'Reject OAuth 2.0 Session Logout RequestWhen a user or an application requests Ory OAuth 2.0 to remove the session state of a subject, this endpoint is used to deny that logout request. No HTTP request body is required. The response is empty as the logout provider has to chose what action to perform next.ory-hydra-client *DELETE /admin/oauth2/auth/sessions/consent.Revoke OAuth 2.0 Consent Sessions of a SubjectThis endpoint revokes a subject's granted consent sessions and invalidates all associated OAuth 2.0 Access Tokens. You may also only revoke sessions for a specific OAuth 2.0 Client ID.ory-hydra-client (DELETE /admin/oauth2/auth/sessions/loginRevokes OAuth 2.0 Login Sessions by either a Subject or a SessionIDThis endpoint invalidates authentication sessions. After revoking the authentication session(s), the subject has to re-authenticate at the Ory OAuth2 Provider. This endpoint does not invalidate any tokens. If you send the subject in a query param, all authentication sessions that belong to that subject are revoked. No OpennID Connect Front- or Back-channel logout is performed in this case. Alternatively, you can send a SessionID via sid query param, in which case, only the session that is connected to that SessionID is revoked. OpenID Connect Back-channel logout is performed in this case.ory-hydra-client POST /oauth2/revoke(Revoke OAuth 2.0 Access or Refresh TokenRevoking 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. AuthMethod: , ory-hydra-client PUT /admin/clients/{id}Set OAuth 2.0 ClientReplaces an existing OAuth 2.0 Client with the payload you send. If you pass  client_secret the secret is used, otherwise the existing secret is used. If set, 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.ory-hydra-client !PUT /admin/clients/{id}/lifespans!Set OAuth2 Client Token LifespansSet lifespans of different token types issued for this OAuth 2.0 client. Does not modify other fields.ory-hydra-client +POST /admin/trust/grants/jwt-bearer/issuers)Trust OAuth2 JWT Bearer Grant Type IssuerUse 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  -https://datatracker.ietf.org/doc/html/rfc7523RFC7523.ory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client Body Param  OAuth2Client - OAuth 2.0 Client Request Bodyory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client !application/x-www-form-urlencodedory-hydra-clientOptional Param "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.ory-hydra-client application/jsonory-hydra-clientOptional Param1 "owner" - The owner of the clients to filter by.ory-hydra-clientOptional Param6 "client_name" - The name of the clients to filter by.ory-hydra-clientOptional Param "page_token" - Next Page Token The next page token. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-clientOptional Param "page_size" - Items per Page This is the number of items per page to return. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client application/jsonory-hydra-clientOptional Param "login_session_id" - The login session id to list the consent sessions for.ory-hydra-clientOptional Param "page_token" - Next Page Token The next page token. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-clientOptional Param "page_size" - Items per Page This is the number of items per page to return. For details on pagination please head over to the  7https://www.ory.sh/docs/ecosystem/api-design#paginationpagination documentation.ory-hydra-client application/jsonory-hydra-clientOptional Param "issuer" - If optional "issuer" is supplied, only jwt-bearer grants with this issuer will be returned.ory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client !application/x-www-form-urlencodedory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client Body Param  JsonPatch# - OAuth 2.0 Client JSON Patch Bodyory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-clientOptional Param0 "all" - Revoke All Consent Sessions If set to true deletes all consent sessions by the Subject that have been granted.ory-hydra-clientOptional Param "client" - OAuth 2.0 Client ID If set, deletes only those consent sessions that have been granted to the specified OAuth 2.0 Client ID.ory-hydra-clientOptional Param "sid" - OAuth 2.0 Subject The subject to revoke authentication sessions for.ory-hydra-clientOptional Param "subject" - OAuth 2.0 Subject The subject to revoke authentication sessions for.ory-hydra-client !application/x-www-form-urlencodedory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client Body Param  OAuth2Client - OAuth 2.0 Client Request Bodyory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client9"consentChallenge" - OAuth 2.0 Consent Request Challengeory-hydra-client5"loginChallenge" - OAuth 2.0 Login Request Challengeory-hydra-client7"logoutChallenge" - OAuth 2.0 Logout Request Challengeory-hydra-client/"oAuth2Client" - OAuth 2.0 Client Request Bodyory-hydra-client'"id" - The id of the OAuth 2.0 Client.ory-hydra-client!"clientId" - OAuth 2.0 Client IDory-hydra-client#"id" - The id of the desired grantory-hydra-client'"id" - The id of the OAuth 2.0 Client.ory-hydra-client9"consentChallenge" - OAuth 2.0 Consent Request Challengeory-hydra-client5"loginChallenge" - OAuth 2.0 Login Request Challengeory-hydra-client"logoutChallenge"ory-hydra-client#"id" - The id of the desired grantory-hydra-client"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.ory-hydra-client:"subject" - The subject to list the consent sessions for.ory-hydra-client "grantType"ory-hydra-client/"jsonPatch" - OAuth 2.0 Client JSON Patch Bodyory-hydra-client'"id" - The id of the OAuth 2.0 Client.ory-hydra-client9"consentChallenge" - OAuth 2.0 Consent Request Challengeory-hydra-client5"loginChallenge" - OAuth 2.0 Login Request Challengeory-hydra-client"logoutChallenge"ory-hydra-client"subject" - OAuth 2.0 Consent Subject The subject whose consent sessions should be deleted.ory-hydra-client"token"ory-hydra-client/"oAuth2Client" - OAuth 2.0 Client Request Bodyory-hydra-client"id" - OAuth 2.0 Client IDory-hydra-client"id" - OAuth 2.0 Client ID88  Safe-Inferred"Ďory-hydra-client  GET /version Return Running Software Version.This endpoint returns the version of Ory Hydra. If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set. Be aware that if you are running multiple nodes of this service, the version will never refer to the cluster state, only to a single instance.ory-hydra-client GET /health/aliveCheck HTTP Server StatusThis endpoint returns a HTTP 200 status code when Ory Hydra is accepting incoming HTTP requests. This status does currently not include checks whether the database connection is working. If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set. Be aware that if you are running multiple nodes of this service, the health status will never refer to the cluster state, only to a single instance.ory-hydra-client GET /health/ready%Check HTTP Server and Database StatusThis endpoint returns a HTTP 200 status code when Ory Hydra is up running and the environment dependencies (e.g. the database) are responsive as well. If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set. Be aware that if you are running multiple nodes of Ory Hydra, the health status will never refer to the cluster state, only to a single instance.ory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/json  Safe-Inferred";ory-hydra-client POST /admin/keys/{set}Create JSON Web KeyThis 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.ory-hydra-client DELETE /admin/keys/{set}/{kid}Delete JSON Web KeyUse 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.ory-hydra-client DELETE /admin/keys/{set}Delete JSON Web Key SetUse 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.ory-hydra-client GET /admin/keys/{set}/{kid}Get JSON Web KeyThis endpoint returns a singular JSON Web Key contained in a set. It is identified by the set and the specific key ID (kid).ory-hydra-client GET /admin/keys/{set}Retrieve a JSON Web Key SetThis 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.ory-hydra-client PUT /admin/keys/{set}/{kid}Set JSON Web KeyUse 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.ory-hydra-client PUT /admin/keys/{set}Update a JSON Web Key SetUse 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.ory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client application/jsonory-hydra-client"createJsonWebKeySet"ory-hydra-client "set" - The JSON Web Key Set IDory-hydra-client"set" - The JSON Web Key Setory-hydra-client""kid" - The JSON Web Key ID (kid)ory-hydra-client"set" - The JSON Web Key Setory-hydra-client"set" - JSON Web Key Set IDory-hydra-client"kid" - JSON Web Key IDory-hydra-client"set" - JSON Web Key Set IDory-hydra-client "set" - The JSON Web Key Set IDory-hydra-client"kid" - JSON Web Key IDory-hydra-client "set" - The JSON Web Key Set ID  Safe-Inferred%&'Չory-hydra-client Lensory-hydra-client Lensory-hydra-client Lensory-hydra-client Lensory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens ory-hydra-client Lens   Safe-Inferred!  !"#$%&'()*+,-./012345[\]^_`abcdefghijklmnotsrpquzyxvw{~|}  Safe-Inferred                  !"#$%&'()**++,,--..//001122345567789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`aabccdeefgghiijjklmnopqrstuvwxyyz{|}~                                                                                                                                /ory-hydra-client-2.1.2.1-CvikDGI3xc5AUqbBqYQIhqORYHydra.LoggingORYHydra.MimeTypes ORYHydra.CoreORYHydra.ClientORYHydra.ModelORYHydra.API.WellknownORYHydra.API.OidcORYHydra.API.OAuth2ORYHydra.API.MetadataORYHydra.API.JwkORYHydra.ModelLensORYHydra.LoggingKatipORYHydraPaths_ory_hydra_clientLogLevel LogContextLogExecLogExecWithContextinitLogContextrunDefaultLogExecWithContextstdoutLoggingExecstdoutLoggingContextstderrLoggingExecstderrLoggingContextrunNullLogExec_log logExceptions levelInfo levelError levelDebug MimeUnrender mimeUnrender mimeUnrender' MimeRender mimeRender mimeRender'MimeType mimeTypesmimeType mimeType' mimeTypes' NoContentMimeAny MimeNoContentMimeOctetStreamMimeMultipartFormDataMimeFormUrlEncoded MimePlainTextMimeXMLMimeJSONProducesConsumesAcceptunAccept ContentType unContentType"mimeRenderDefaultMultipartFormData$fMimeTypeMimeNoContent$fMimeTypeMimeAny$fMimeTypeMimeOctetStream$fMimeTypeMimePlainText$fMimeTypeMimeMultipartFormData$fMimeTypeMimeFormUrlEncoded$fMimeTypeMimeXML$fMimeTypeMimeJSON"$fMimeRenderMimeNoContentNoContent%$fMimeRenderMimeMultipartFormDataText#$fMimeRenderMimeMultipartFormData[]($fMimeRenderMimeMultipartFormDataInteger$$fMimeRenderMimeMultipartFormDataInt&$fMimeRenderMimeMultipartFormDataFloat'$fMimeRenderMimeMultipartFormDataDouble%$fMimeRenderMimeMultipartFormDataChar%$fMimeRenderMimeMultipartFormDataBool+$fMimeRenderMimeMultipartFormDataByteString$fMimeRenderMimeOctetStream[]$fMimeRenderMimeOctetStreamText%$fMimeRenderMimeOctetStreamByteString$fMimeRenderMimePlainText[]$fMimeRenderMimePlainTextText#$fMimeRenderMimePlainTextByteString$fMimeRenderMimeFormUrlEncodeda$fMimeRenderMimeJSONa$$fMimeUnrenderMimeNoContentNoContent$fMimeUnrenderMimeOctetStream[]!$fMimeUnrenderMimeOctetStreamText'$fMimeUnrenderMimeOctetStreamByteString$fMimeUnrenderMimePlainText[]$fMimeUnrenderMimePlainTextText%$fMimeUnrenderMimePlainTextByteString!$fMimeUnrenderMimeFormUrlEncodeda$fMimeUnrenderMimeJSONa$fShowNoContent $fEqNoContentLens_Lens_'BinaryunBinary ByteArray unByteArrayDateunDateDateTime unDateTimeAuthMethodException AnyAuthMethod AuthMethodapplyAuthMethodCollectionFormatCommaSeparatedSpaceSeparated TabSeparated PipeSeparatedMultiParamArray ParamBody ParamBodyNone ParamBodyB ParamBodyBLParamBodyFormUrlEncodedParamBodyMultipartFormDataParams paramsQuery paramsHeaders paramsBodyHasOptionalParamapplyOptionalParam-&- HasBodyParam setBodyParamORYHydraRequestrMethodrUrlPathrParams rAuthTypesORYHydraConfig configHostconfigUserAgentconfigLogExecWithContextconfigLogContextconfigAuthMethodsconfigValidateAuthMethodsconfigQueryExtraUnreserved newConfig addAuthMethodwithStdoutLoggingwithStderrLogging withNoLoggingrMethodL rUrlPathLrParamsL rAuthTypesL paramsQueryLparamsHeadersL paramsBodyL _mkRequest _mkParams setHeader addHeader removeHeader_setContentTypeHeader_setAcceptHeadersetQueryaddQueryaddForm_addMultiFormPart _setBodyBS _setBodyLBS _hasAuthTypetoPathtoHeadertoFormtoQuerytoPartialEscapeQuery toHeaderColl toFormColl toQueryColl_toColl_toCollA _toCollA'_applyAuthMethods _omitNulls _toFormItem_emptyToNothing_memptyToNothing _readDateTime _showDateTime _parseISO8601 _readDate _showDate_readByteArray_showByteArray_readBinaryBase64_showBinaryBase64$fAuthMethodAnyAuthMethod$fShowORYHydraConfig$fExceptionAuthMethodException)$fMimeRenderMimeMultipartFormDataDateTime$fShowDateTime$fToHttpApiDataDateTime$fFromHttpApiDataDateTime$fToJSONDateTime$fFromJSONDateTime%$fMimeRenderMimeMultipartFormDataDate $fShowDate$fToHttpApiDataDate$fFromHttpApiDataDate $fToJSONDate$fFromJSONDate*$fMimeRenderMimeMultipartFormDataByteArray$fShowByteArray$fToHttpApiDataByteArray$fFromHttpApiDataByteArray$fToJSONByteArray$fFromJSONByteArray'$fMimeRenderMimeMultipartFormDataBinary $fShowBinary$fToHttpApiDataBinary$fFromHttpApiDataBinary$fToJSONBinary$fFromJSONBinary $fEqBinary $fDataBinary $fOrdBinary$fNFDataBinary $fEqByteArray$fDataByteArray$fOrdByteArray$fNFDataByteArray $fEnumDate$fEqDate $fDataDate $fOrdDate$fIxDate $fNFDataDate $fEqDateTime$fDataDateTime $fOrdDateTime$fNFDataDateTime$fShowAuthMethodException$fShowORYHydraRequest $fShowParams$fShowParamBody InitRequest unInitRequest MimeError mimeErrormimeErrorResponse MimeResult mimeResultmimeResultResponse dispatchLbs dispatchMime dispatchMime'dispatchLbsUnsafedispatchInitUnsafe_toInitRequestmodifyInitRequestmodifyInitRequestM runConfigLogrunConfigLogWithExceptions$fShowInitRequest$fShowMimeResult$fFunctorMimeResult$fFoldableMimeResult$fTraversableMimeResult$fShowMimeErrorAuthOAuthOauth2AuthBasicBearerAuthBasicBasicVersionversionVersionTrustedOAuth2JwtGrantJsonWebKey"trustedOAuth2JwtGrantJsonWebKeyKid"trustedOAuth2JwtGrantJsonWebKeySetTrustedOAuth2JwtGrantIssuer*trustedOAuth2JwtGrantIssuerAllowAnySubject$trustedOAuth2JwtGrantIssuerCreatedAt$trustedOAuth2JwtGrantIssuerExpiresAttrustedOAuth2JwtGrantIssuerId!trustedOAuth2JwtGrantIssuerIssuer$trustedOAuth2JwtGrantIssuerPublicKey trustedOAuth2JwtGrantIssuerScope"trustedOAuth2JwtGrantIssuerSubjectTrustOAuth2JwtGrantIssuer(trustOAuth2JwtGrantIssuerAllowAnySubject"trustOAuth2JwtGrantIssuerExpiresAttrustOAuth2JwtGrantIssuerIssuertrustOAuth2JwtGrantIssuerJwktrustOAuth2JwtGrantIssuerScope trustOAuth2JwtGrantIssuerSubjectTokenPaginationResponseHeaders"tokenPaginationResponseHeadersLink)tokenPaginationResponseHeadersXTotalCount TokenPaginationRequestParameters(tokenPaginationRequestParametersPageSize)tokenPaginationRequestParametersPageTokenTokenPaginationHeaderstokenPaginationHeadersLink!tokenPaginationHeadersXTotalCountTokenPaginationtokenPaginationPageSizetokenPaginationPageTokenRejectOAuth2RequestrejectOAuth2RequestErrorrejectOAuth2RequestErrorDebug#rejectOAuth2RequestErrorDescriptionrejectOAuth2RequestErrorHintrejectOAuth2RequestStatusCodePaginationHeaderspaginationHeadersLinkpaginationHeadersXTotalCount PaginationpaginationPageSizepaginationPageToken OidcUserInfooidcUserInfoBirthdateoidcUserInfoEmailoidcUserInfoEmailVerifiedoidcUserInfoFamilyNameoidcUserInfoGenderoidcUserInfoGivenNameoidcUserInfoLocaleoidcUserInfoMiddleNameoidcUserInfoNameoidcUserInfoNicknameoidcUserInfoPhoneNumberoidcUserInfoPhoneNumberVerifiedoidcUserInfoPictureoidcUserInfoPreferredUsernameoidcUserInfoProfileoidcUserInfoSuboidcUserInfoUpdatedAtoidcUserInfoWebsiteoidcUserInfoZoneinfoOidcConfiguration&oidcConfigurationAuthorizationEndpoint2oidcConfigurationBackchannelLogoutSessionSupported+oidcConfigurationBackchannelLogoutSupported)oidcConfigurationClaimsParameterSupported oidcConfigurationClaimsSupported.oidcConfigurationCodeChallengeMethodsSupported#oidcConfigurationEndSessionEndpoint3oidcConfigurationFrontchannelLogoutSessionSupported,oidcConfigurationFrontchannelLogoutSupported$oidcConfigurationGrantTypesSupported)oidcConfigurationIdTokenSignedResponseAlg1oidcConfigurationIdTokenSigningAlgValuesSupportedoidcConfigurationIssueroidcConfigurationJwksUri%oidcConfigurationRegistrationEndpoint7oidcConfigurationRequestObjectSigningAlgValuesSupported*oidcConfigurationRequestParameterSupported-oidcConfigurationRequestUriParameterSupported.oidcConfigurationRequireRequestUriRegistration'oidcConfigurationResponseModesSupported'oidcConfigurationResponseTypesSupported#oidcConfigurationRevocationEndpoint oidcConfigurationScopesSupported&oidcConfigurationSubjectTypesSupportedoidcConfigurationTokenEndpoint2oidcConfigurationTokenEndpointAuthMethodsSupported!oidcConfigurationUserinfoEndpoint*oidcConfigurationUserinfoSignedResponseAlg2oidcConfigurationUserinfoSigningAlgValuesSupportedOAuth2TokenExchangeoAuth2TokenExchangeAccessTokenoAuth2TokenExchangeExpiresInoAuth2TokenExchangeIdTokenoAuth2TokenExchangeRefreshTokenoAuth2TokenExchangeScopeoAuth2TokenExchangeTokenTypeOAuth2RedirectTooAuth2RedirectToRedirectToOAuth2LogoutRequestoAuth2LogoutRequestChallengeoAuth2LogoutRequestClientoAuth2LogoutRequestRequestUrloAuth2LogoutRequestRpInitiatedoAuth2LogoutRequestSidoAuth2LogoutRequestSubjectOAuth2LoginRequestoAuth2LoginRequestChallengeoAuth2LoginRequestClientoAuth2LoginRequestOidcContextoAuth2LoginRequestRequestUrl.oAuth2LoginRequestRequestedAccessTokenAudience oAuth2LoginRequestRequestedScopeoAuth2LoginRequestSessionIdoAuth2LoginRequestSkipoAuth2LoginRequestSubjectOAuth2ConsentSessionExpiresAt(oAuth2ConsentSessionExpiresAtAccessToken*oAuth2ConsentSessionExpiresAtAuthorizeCode$oAuth2ConsentSessionExpiresAtIdToken'oAuth2ConsentSessionExpiresAtParContext)oAuth2ConsentSessionExpiresAtRefreshTokenOAuth2ConsentSession"oAuth2ConsentSessionConsentRequestoAuth2ConsentSessionExpiresAt,oAuth2ConsentSessionGrantAccessTokenAudienceoAuth2ConsentSessionGrantScopeoAuth2ConsentSessionHandledAtoAuth2ConsentSessionRememberoAuth2ConsentSessionRememberForoAuth2ConsentSessionSession(OAuth2ConsentRequestOpenIDConnectContext1oAuth2ConsentRequestOpenIDConnectContextAcrValues/oAuth2ConsentRequestOpenIDConnectContextDisplay9oAuth2ConsentRequestOpenIDConnectContextIdTokenHintClaims1oAuth2ConsentRequestOpenIDConnectContextLoginHint1oAuth2ConsentRequestOpenIDConnectContextUiLocalesOAuth2ConsentRequestoAuth2ConsentRequestAcroAuth2ConsentRequestAmroAuth2ConsentRequestChallengeoAuth2ConsentRequestClientoAuth2ConsentRequestContext"oAuth2ConsentRequestLoginChallenge"oAuth2ConsentRequestLoginSessionIdoAuth2ConsentRequestOidcContextoAuth2ConsentRequestRequestUrl0oAuth2ConsentRequestRequestedAccessTokenAudience"oAuth2ConsentRequestRequestedScopeoAuth2ConsentRequestSkipoAuth2ConsentRequestSubjectOAuth2ClientTokenLifespansoAuth2ClientTokenLifespansAuthorizationCodeGrantAccessTokenLifespan?oAuth2ClientTokenLifespansAuthorizationCodeGrantIdTokenLifespanoAuth2ClientTokenLifespansAuthorizationCodeGrantRefreshTokenLifespanoAuth2ClientTokenLifespansClientCredentialsGrantAccessTokenLifespan:oAuth2ClientTokenLifespansImplicitGrantAccessTokenLifespan6oAuth2ClientTokenLifespansImplicitGrantIdTokenLifespan;oAuth2ClientTokenLifespansJwtBearerGrantAccessTokenLifespan>oAuth2ClientTokenLifespansRefreshTokenGrantAccessTokenLifespan:oAuth2ClientTokenLifespansRefreshTokenGrantIdTokenLifespan?oAuth2ClientTokenLifespansRefreshTokenGrantRefreshTokenLifespan OAuth2ClientoAuth2ClientAccessTokenStrategyoAuth2ClientAllowedCorsOriginsoAuth2ClientAudience5oAuth2ClientAuthorizationCodeGrantAccessTokenLifespan1oAuth2ClientAuthorizationCodeGrantIdTokenLifespan6oAuth2ClientAuthorizationCodeGrantRefreshTokenLifespan,oAuth2ClientBackchannelLogoutSessionRequired oAuth2ClientBackchannelLogoutUri5oAuth2ClientClientCredentialsGrantAccessTokenLifespanoAuth2ClientClientIdoAuth2ClientClientNameoAuth2ClientClientSecret!oAuth2ClientClientSecretExpiresAtoAuth2ClientClientUrioAuth2ClientContactsoAuth2ClientCreatedAt-oAuth2ClientFrontchannelLogoutSessionRequired!oAuth2ClientFrontchannelLogoutUrioAuth2ClientGrantTypes,oAuth2ClientImplicitGrantAccessTokenLifespan(oAuth2ClientImplicitGrantIdTokenLifespanoAuth2ClientJwksoAuth2ClientJwksUri-oAuth2ClientJwtBearerGrantAccessTokenLifespanoAuth2ClientLogoUrioAuth2ClientMetadataoAuth2ClientOwneroAuth2ClientPolicyUri"oAuth2ClientPostLogoutRedirectUrisoAuth2ClientRedirectUris0oAuth2ClientRefreshTokenGrantAccessTokenLifespan,oAuth2ClientRefreshTokenGrantIdTokenLifespan1oAuth2ClientRefreshTokenGrantRefreshTokenLifespan#oAuth2ClientRegistrationAccessToken!oAuth2ClientRegistrationClientUri#oAuth2ClientRequestObjectSigningAlgoAuth2ClientRequestUrisoAuth2ClientResponseTypesoAuth2ClientScopeoAuth2ClientSectorIdentifierUrioAuth2ClientSkipConsentoAuth2ClientSubjectType#oAuth2ClientTokenEndpointAuthMethod'oAuth2ClientTokenEndpointAuthSigningAlgoAuth2ClientTosUrioAuth2ClientUpdatedAt%oAuth2ClientUserinfoSignedResponseAlg JsonWebKeySetjsonWebKeySetKeys JsonWebKey jsonWebKeyAlg jsonWebKeyCrv jsonWebKeyD jsonWebKeyDp jsonWebKeyDq jsonWebKeyE jsonWebKeyK jsonWebKeyKid jsonWebKeyKty jsonWebKeyN jsonWebKeyP jsonWebKeyQ jsonWebKeyQi jsonWebKeyUse jsonWebKeyX jsonWebKeyX5c jsonWebKeyY JsonPatch jsonPatchFrom jsonPatchOp jsonPatchPathjsonPatchValueIsReady503ResponseisReady503ResponseErrorsIsReady200ResponseisReady200ResponseStatusIntrospectedOAuth2TokenintrospectedOAuth2TokenActiveintrospectedOAuth2TokenAudintrospectedOAuth2TokenClientIdintrospectedOAuth2TokenExpintrospectedOAuth2TokenExtintrospectedOAuth2TokenIatintrospectedOAuth2TokenIssintrospectedOAuth2TokenNbf(introspectedOAuth2TokenObfuscatedSubjectintrospectedOAuth2TokenScopeintrospectedOAuth2TokenSub introspectedOAuth2TokenTokenTypeintrospectedOAuth2TokenTokenUseintrospectedOAuth2TokenUsername HealthStatushealthStatusStatusHealthNotReadyStatushealthNotReadyStatusErrorsGetVersion200ResponsegetVersion200ResponseVersion GenericErrorgenericErrorCodegenericErrorDebuggenericErrorDetailsgenericErrorIdgenericErrorMessagegenericErrorReasongenericErrorRequestgenericErrorStatus ErrorOAuth2errorOAuth2ErrorerrorOAuth2ErrorDebugerrorOAuth2ErrorDescriptionerrorOAuth2ErrorHinterrorOAuth2StatusCodeCreateJsonWebKeySetcreateJsonWebKeySetAlgcreateJsonWebKeySetKidcreateJsonWebKeySetUseAcceptOAuth2LoginRequestacceptOAuth2LoginRequestAcracceptOAuth2LoginRequestAmracceptOAuth2LoginRequestContext-acceptOAuth2LoginRequestExtendSessionLifespan.acceptOAuth2LoginRequestForceSubjectIdentifier acceptOAuth2LoginRequestRemember#acceptOAuth2LoginRequestRememberForacceptOAuth2LoginRequestSubject!AcceptOAuth2ConsentRequestSession,acceptOAuth2ConsentRequestSessionAccessToken(acceptOAuth2ConsentRequestSessionIdTokenAcceptOAuth2ConsentRequest2acceptOAuth2ConsentRequestGrantAccessTokenAudience$acceptOAuth2ConsentRequestGrantScope#acceptOAuth2ConsentRequestHandledAt"acceptOAuth2ConsentRequestRemember%acceptOAuth2ConsentRequestRememberFor!acceptOAuth2ConsentRequestSessionTokenunTokenSubject unSubjectSidunSidSetunSetScopeunScope RefreshTokenunRefreshToken RedirectUri unRedirectUri PageToken unPageTokenPageSize unPageSizeOwnerunOwnerMaxItems unMaxItemsLogoutChallengeunLogoutChallengeLoginSessionIdunLoginSessionIdLoginChallengeunLoginChallengeKidunKid JsonPatch2 unJsonPatch2IssuerunIssuerIdunId GrantType unGrantType DefaultItemsunDefaultItemsConsentChallengeunConsentChallengeCodeunCode ClientSecretunClientSecret ClientName unClientNameClientId unClientIdClientunClientAllunAllmkAcceptOAuth2ConsentRequest#mkAcceptOAuth2ConsentRequestSessionmkAcceptOAuth2LoginRequestmkCreateJsonWebKeySet mkErrorOAuth2mkGenericErrormkGetVersion200ResponsemkHealthNotReadyStatusmkHealthStatusmkIntrospectedOAuth2TokenmkIsReady200ResponsemkIsReady503Response mkJsonPatch mkJsonWebKeymkJsonWebKeySetmkOAuth2ClientmkOAuth2ClientTokenLifespansmkOAuth2ConsentRequest*mkOAuth2ConsentRequestOpenIDConnectContextmkOAuth2ConsentSessionmkOAuth2ConsentSessionExpiresAtmkOAuth2LoginRequestmkOAuth2LogoutRequestmkOAuth2RedirectTomkOAuth2TokenExchangemkOidcConfigurationmkOidcUserInfo mkPaginationmkPaginationHeadersmkRejectOAuth2RequestmkTokenPaginationmkTokenPaginationHeaders"mkTokenPaginationRequestParameters mkTokenPaginationResponseHeadersmkTrustOAuth2JwtGrantIssuermkTrustedOAuth2JwtGrantIssuer!mkTrustedOAuth2JwtGrantJsonWebKey mkVersion)$fToJSONAcceptOAuth2ConsentRequestSession+$fFromJSONAcceptOAuth2ConsentRequestSession"$fToJSONAcceptOAuth2ConsentRequest$$fFromJSONAcceptOAuth2ConsentRequest $fToJSONAcceptOAuth2LoginRequest"$fFromJSONAcceptOAuth2LoginRequest$fToJSONCreateJsonWebKeySet$fFromJSONCreateJsonWebKeySet$fToJSONErrorOAuth2$fFromJSONErrorOAuth2$fToJSONGenericError$fFromJSONGenericError$fToJSONGetVersion200Response$fFromJSONGetVersion200Response$fToJSONHealthNotReadyStatus$fFromJSONHealthNotReadyStatus$fToJSONHealthStatus$fFromJSONHealthStatus$fToJSONIntrospectedOAuth2Token!$fFromJSONIntrospectedOAuth2Token$fToJSONIsReady200Response$fFromJSONIsReady200Response$fToJSONIsReady503Response$fFromJSONIsReady503Response$fToJSONJsonPatch$fFromJSONJsonPatch$fToJSONJsonWebKey$fFromJSONJsonWebKey$fToJSONJsonWebKeySet$fFromJSONJsonWebKeySet$fToJSONOAuth2Client$fFromJSONOAuth2Client"$fToJSONOAuth2ClientTokenLifespans$$fFromJSONOAuth2ClientTokenLifespans0$fToJSONOAuth2ConsentRequestOpenIDConnectContext2$fFromJSONOAuth2ConsentRequestOpenIDConnectContext$fToJSONOAuth2ConsentRequest$fFromJSONOAuth2ConsentRequest%$fToJSONOAuth2ConsentSessionExpiresAt'$fFromJSONOAuth2ConsentSessionExpiresAt$fToJSONOAuth2ConsentSession$fFromJSONOAuth2ConsentSession$fToJSONOAuth2LoginRequest$fFromJSONOAuth2LoginRequest$fToJSONOAuth2LogoutRequest$fFromJSONOAuth2LogoutRequest$fToJSONOAuth2RedirectTo$fFromJSONOAuth2RedirectTo$fToJSONOAuth2TokenExchange$fFromJSONOAuth2TokenExchange$fToJSONOidcConfiguration$fFromJSONOidcConfiguration$fToJSONOidcUserInfo$fFromJSONOidcUserInfo$fToJSONPagination$fFromJSONPagination$fToJSONPaginationHeaders$fFromJSONPaginationHeaders$fToJSONRejectOAuth2Request$fFromJSONRejectOAuth2Request$fToJSONTokenPagination$fFromJSONTokenPagination$fToJSONTokenPaginationHeaders $fFromJSONTokenPaginationHeaders($fToJSONTokenPaginationRequestParameters*$fFromJSONTokenPaginationRequestParameters&$fToJSONTokenPaginationResponseHeaders($fFromJSONTokenPaginationResponseHeaders!$fToJSONTrustOAuth2JwtGrantIssuer#$fFromJSONTrustOAuth2JwtGrantIssuer'$fToJSONTrustedOAuth2JwtGrantJsonWebKey)$fFromJSONTrustedOAuth2JwtGrantJsonWebKey#$fToJSONTrustedOAuth2JwtGrantIssuer%$fFromJSONTrustedOAuth2JwtGrantIssuer$fToJSONVersion$fFromJSONVersion$fAuthMethodAuthBasicBasic$fAuthMethodAuthBasicBearer$fAuthMethodAuthOAuthOauth2$fEqAuthOAuthOauth2$fShowAuthOAuthOauth2$fEqAuthBasicBearer$fShowAuthBasicBearer$fEqAuthBasicBasic$fShowAuthBasicBasic $fShowVersion $fEqVersion!$fShowTrustedOAuth2JwtGrantIssuer$fEqTrustedOAuth2JwtGrantIssuer%$fShowTrustedOAuth2JwtGrantJsonWebKey#$fEqTrustedOAuth2JwtGrantJsonWebKey$fShowTrustOAuth2JwtGrantIssuer$fEqTrustOAuth2JwtGrantIssuer$$fShowTokenPaginationResponseHeaders"$fEqTokenPaginationResponseHeaders&$fShowTokenPaginationRequestParameters$$fEqTokenPaginationRequestParameters$fShowTokenPaginationHeaders$fEqTokenPaginationHeaders$fShowTokenPagination$fEqTokenPagination$fShowRejectOAuth2Request$fEqRejectOAuth2Request$fShowPaginationHeaders$fEqPaginationHeaders$fShowPagination$fEqPagination$fShowOidcUserInfo$fEqOidcUserInfo$fShowOidcConfiguration$fEqOidcConfiguration$fShowOAuth2TokenExchange$fEqOAuth2TokenExchange$fShowOAuth2RedirectTo$fEqOAuth2RedirectTo$fShowOAuth2LogoutRequest$fEqOAuth2LogoutRequest$fShowOAuth2LoginRequest$fEqOAuth2LoginRequest$fShowOAuth2ConsentSession$fEqOAuth2ConsentSession#$fShowOAuth2ConsentSessionExpiresAt!$fEqOAuth2ConsentSessionExpiresAt$fShowOAuth2ConsentRequest$fEqOAuth2ConsentRequest.$fShowOAuth2ConsentRequestOpenIDConnectContext,$fEqOAuth2ConsentRequestOpenIDConnectContext $fShowOAuth2ClientTokenLifespans$fEqOAuth2ClientTokenLifespans$fShowOAuth2Client$fEqOAuth2Client$fShowJsonWebKeySet$fEqJsonWebKeySet$fShowJsonWebKey$fEqJsonWebKey$fEqJsonPatch2$fShowJsonPatch2$fToJSONJsonPatch2$fShowJsonPatch $fEqJsonPatch$fShowIsReady503Response$fEqIsReady503Response$fShowIsReady200Response$fEqIsReady200Response$fShowIntrospectedOAuth2Token$fEqIntrospectedOAuth2Token$fShowHealthStatus$fEqHealthStatus$fShowHealthNotReadyStatus$fEqHealthNotReadyStatus$fShowGetVersion200Response$fEqGetVersion200Response$fShowGenericError$fEqGenericError$fShowErrorOAuth2$fEqErrorOAuth2$fShowCreateJsonWebKeySet$fEqCreateJsonWebKeySet$fShowAcceptOAuth2LoginRequest$fEqAcceptOAuth2LoginRequest $fShowAcceptOAuth2ConsentRequest$fEqAcceptOAuth2ConsentRequest'$fShowAcceptOAuth2ConsentRequestSession%$fEqAcceptOAuth2ConsentRequestSession $fEqToken $fShowToken $fEqSubject $fShowSubject$fEqSid $fShowSid$fEqSet $fShowSet $fEqScope $fShowScope$fEqRefreshToken$fShowRefreshToken$fEqRedirectUri$fShowRedirectUri $fEqPageToken$fShowPageToken $fEqPageSize$fShowPageSize $fEqOwner $fShowOwner $fEqMaxItems$fShowMaxItems$fEqLogoutChallenge$fShowLogoutChallenge$fEqLoginSessionId$fShowLoginSessionId$fEqLoginChallenge$fShowLoginChallenge$fEqKid $fShowKid $fEqIssuer $fShowIssuer$fEqId$fShowId $fEqGrantType$fShowGrantType$fEqDefaultItems$fShowDefaultItems$fEqConsentChallenge$fShowConsentChallenge$fEqCode $fShowCode$fEqClientSecret$fShowClientSecret$fEqClientName$fShowClientName $fEqClientId$fShowClientId $fEqClient $fShowClient$fEqAll $fShowAllDiscoverJsonWebKeysdiscoverJsonWebKeys%$fProducesDiscoverJsonWebKeysMimeJSONSetOidcDynamicClientRevokeOidcSessionGetOidcUserInfoGetOidcDynamicClientDiscoverOidcConfigurationDeleteOidcDynamicClientCreateOidcDynamicClientcreateOidcDynamicClientdeleteOidcDynamicClientdiscoverOidcConfigurationgetOidcDynamicClientgetOidcUserInforevokeOidcSessionsetOidcDynamicClient)$fProducesCreateOidcDynamicClientMimeJSON)$fConsumesCreateOidcDynamicClientMimeJSON1$fHasBodyParamCreateOidcDynamicClientOAuth2Client.$fProducesDeleteOidcDynamicClientMimeNoContent+$fProducesDiscoverOidcConfigurationMimeJSON&$fProducesGetOidcDynamicClientMimeJSON!$fProducesGetOidcUserInfoMimeJSON($fProducesRevokeOidcSessionMimeNoContent&$fProducesSetOidcDynamicClientMimeJSON&$fConsumesSetOidcDynamicClientMimeJSON.$fHasBodyParamSetOidcDynamicClientOAuth2ClientTrustOAuth2JwtGrantIssuer0SetOAuth2ClientLifespansSetOAuth2ClientRevokeOAuth2TokenRevokeOAuth2LoginSessionsRevokeOAuth2ConsentSessionsRejectOAuth2LogoutRequestRejectOAuth2LoginRequestRejectOAuth2ConsentRequestPatchOAuth2ClientOauth2TokenExchangeOAuth2Authorize ListTrustedOAuth2JwtGrantIssuersListOAuth2ConsentSessionsListOAuth2ClientsIntrospectOAuth2TokenGetTrustedOAuth2JwtGrantIssuerGetOAuth2LogoutRequestGetOAuth2LoginRequestGetOAuth2ConsentRequestGetOAuth2Client!DeleteTrustedOAuth2JwtGrantIssuerDeleteOAuth2TokenDeleteOAuth2ClientCreateOAuth2ClientAcceptOAuth2LogoutRequestAcceptOAuth2LoginRequest0AcceptOAuth2ConsentRequest0acceptOAuth2ConsentRequest0acceptOAuth2LoginRequest0acceptOAuth2LogoutRequestcreateOAuth2ClientdeleteOAuth2ClientdeleteOAuth2Token!deleteTrustedOAuth2JwtGrantIssuergetOAuth2ClientgetOAuth2ConsentRequestgetOAuth2LoginRequestgetOAuth2LogoutRequestgetTrustedOAuth2JwtGrantIssuerintrospectOAuth2TokenlistOAuth2ClientslistOAuth2ConsentSessions listTrustedOAuth2JwtGrantIssuersoAuth2Authorizeoauth2TokenExchangepatchOAuth2ClientrejectOAuth2ConsentRequestrejectOAuth2LoginRequestrejectOAuth2LogoutRequestrevokeOAuth2ConsentSessionsrevokeOAuth2LoginSessionsrevokeOAuth2TokensetOAuth2ClientsetOAuth2ClientLifespanstrustOAuth2JwtGrantIssuer0-$fProducesAcceptOAuth2ConsentRequest0MimeJSON-$fConsumesAcceptOAuth2ConsentRequest0MimeJSON$fHasBodyParamAcceptOAuth2ConsentRequest0AcceptOAuth2ConsentRequest+$fProducesAcceptOAuth2LoginRequest0MimeJSON+$fConsumesAcceptOAuth2LoginRequest0MimeJSON?$fHasBodyParamAcceptOAuth2LoginRequest0AcceptOAuth2LoginRequest+$fProducesAcceptOAuth2LogoutRequestMimeJSON$$fProducesCreateOAuth2ClientMimeJSON$$fConsumesCreateOAuth2ClientMimeJSON,$fHasBodyParamCreateOAuth2ClientOAuth2Client)$fProducesDeleteOAuth2ClientMimeNoContent($fProducesDeleteOAuth2TokenMimeNoContent8$fProducesDeleteTrustedOAuth2JwtGrantIssuerMimeNoContent!$fProducesGetOAuth2ClientMimeJSON)$fProducesGetOAuth2ConsentRequestMimeJSON'$fProducesGetOAuth2LoginRequestMimeJSON($fProducesGetOAuth2LogoutRequestMimeJSON0$fProducesGetTrustedOAuth2JwtGrantIssuerMimeJSON'$fProducesIntrospectOAuth2TokenMimeJSON1$fConsumesIntrospectOAuth2TokenMimeFormUrlEncoded,$fHasOptionalParamIntrospectOAuth2TokenScope#$fProducesListOAuth2ClientsMimeJSON($fHasOptionalParamListOAuth2ClientsOwner-$fHasOptionalParamListOAuth2ClientsClientName,$fHasOptionalParamListOAuth2ClientsPageToken+$fHasOptionalParamListOAuth2ClientsPageSize+$fProducesListOAuth2ConsentSessionsMimeJSON9$fHasOptionalParamListOAuth2ConsentSessionsLoginSessionId4$fHasOptionalParamListOAuth2ConsentSessionsPageToken3$fHasOptionalParamListOAuth2ConsentSessionsPageSize2$fProducesListTrustedOAuth2JwtGrantIssuersMimeJSON8$fHasOptionalParamListTrustedOAuth2JwtGrantIssuersIssuer>$fHasOptionalParamListTrustedOAuth2JwtGrantIssuersDefaultItems:$fHasOptionalParamListTrustedOAuth2JwtGrantIssuersMaxItems!$fProducesOAuth2AuthorizeMimeJSON%$fProducesOauth2TokenExchangeMimeJSON/$fConsumesOauth2TokenExchangeMimeFormUrlEncoded1$fHasOptionalParamOauth2TokenExchangeRefreshToken0$fHasOptionalParamOauth2TokenExchangeRedirectUri)$fHasOptionalParamOauth2TokenExchangeCode-$fHasOptionalParamOauth2TokenExchangeClientId#$fProducesPatchOAuth2ClientMimeJSON#$fConsumesPatchOAuth2ClientMimeJSON)$fHasBodyParamPatchOAuth2ClientJsonPatch2,$fProducesRejectOAuth2ConsentRequestMimeJSON,$fConsumesRejectOAuth2ConsentRequestMimeJSON;$fHasBodyParamRejectOAuth2ConsentRequestRejectOAuth2Request*$fProducesRejectOAuth2LoginRequestMimeJSON*$fConsumesRejectOAuth2LoginRequestMimeJSON9$fHasBodyParamRejectOAuth2LoginRequestRejectOAuth2Request0$fProducesRejectOAuth2LogoutRequestMimeNoContent2$fProducesRevokeOAuth2ConsentSessionsMimeNoContent0$fHasOptionalParamRevokeOAuth2ConsentSessionsAll3$fHasOptionalParamRevokeOAuth2ConsentSessionsClient0$fProducesRevokeOAuth2LoginSessionsMimeNoContent.$fHasOptionalParamRevokeOAuth2LoginSessionsSid2$fHasOptionalParamRevokeOAuth2LoginSessionsSubject($fProducesRevokeOAuth2TokenMimeNoContent-$fConsumesRevokeOAuth2TokenMimeFormUrlEncoded/$fHasOptionalParamRevokeOAuth2TokenClientSecret+$fHasOptionalParamRevokeOAuth2TokenClientId!$fProducesSetOAuth2ClientMimeJSON!$fConsumesSetOAuth2ClientMimeJSON)$fHasBodyParamSetOAuth2ClientOAuth2Client*$fProducesSetOAuth2ClientLifespansMimeJSON*$fConsumesSetOAuth2ClientLifespansMimeJSON$fHasBodyParamSetOAuth2ClientLifespansOAuth2ClientTokenLifespans,$fProducesTrustOAuth2JwtGrantIssuer0MimeJSON,$fConsumesTrustOAuth2JwtGrantIssuer0MimeJSON$fHasBodyParamTrustOAuth2JwtGrantIssuer0TrustOAuth2JwtGrantIssuerIsReadyIsAlive GetVersion getVersionisAliveisReady$fProducesGetVersionMimeJSON$fProducesIsAliveMimeJSON$fProducesIsReadyMimeJSONSetJsonWebKeySet SetJsonWebKeyGetJsonWebKeySet GetJsonWebKeyDeleteJsonWebKeySetDeleteJsonWebKeyCreateJsonWebKeySet0createJsonWebKeySet0deleteJsonWebKeydeleteJsonWebKeySet getJsonWebKeygetJsonWebKeySet setJsonWebKeysetJsonWebKeySet&$fProducesCreateJsonWebKeySet0MimeJSON&$fConsumesCreateJsonWebKeySet0MimeJSON5$fHasBodyParamCreateJsonWebKeySet0CreateJsonWebKeySet'$fProducesDeleteJsonWebKeyMimeNoContent*$fProducesDeleteJsonWebKeySetMimeNoContent$fProducesGetJsonWebKeyMimeJSON"$fProducesGetJsonWebKeySetMimeJSON$fProducesSetJsonWebKeyMimeJSON$fConsumesSetJsonWebKeyMimeJSON%$fHasBodyParamSetJsonWebKeyJsonWebKey"$fProducesSetJsonWebKeySetMimeJSON"$fConsumesSetJsonWebKeySetMimeJSON+$fHasBodyParamSetJsonWebKeySetJsonWebKeySet3acceptOAuth2ConsentRequestGrantAccessTokenAudienceL%acceptOAuth2ConsentRequestGrantScopeL$acceptOAuth2ConsentRequestHandledAtL#acceptOAuth2ConsentRequestRememberL&acceptOAuth2ConsentRequestRememberForL"acceptOAuth2ConsentRequestSessionL-acceptOAuth2ConsentRequestSessionAccessTokenL)acceptOAuth2ConsentRequestSessionIdTokenLacceptOAuth2LoginRequestAcrLacceptOAuth2LoginRequestAmrL acceptOAuth2LoginRequestContextL.acceptOAuth2LoginRequestExtendSessionLifespanL/acceptOAuth2LoginRequestForceSubjectIdentifierL!acceptOAuth2LoginRequestRememberL$acceptOAuth2LoginRequestRememberForL acceptOAuth2LoginRequestSubjectLcreateJsonWebKeySetAlgLcreateJsonWebKeySetKidLcreateJsonWebKeySetUseLerrorOAuth2ErrorLerrorOAuth2ErrorDebugLerrorOAuth2ErrorDescriptionLerrorOAuth2ErrorHintLerrorOAuth2StatusCodeLgenericErrorCodeLgenericErrorDebugLgenericErrorDetailsLgenericErrorIdLgenericErrorMessageLgenericErrorReasonLgenericErrorRequestLgenericErrorStatusLgetVersion200ResponseVersionLhealthNotReadyStatusErrorsLhealthStatusStatusLintrospectedOAuth2TokenActiveLintrospectedOAuth2TokenAudL introspectedOAuth2TokenClientIdLintrospectedOAuth2TokenExpLintrospectedOAuth2TokenExtLintrospectedOAuth2TokenIatLintrospectedOAuth2TokenIssLintrospectedOAuth2TokenNbfL)introspectedOAuth2TokenObfuscatedSubjectLintrospectedOAuth2TokenScopeLintrospectedOAuth2TokenSubL!introspectedOAuth2TokenTokenTypeL introspectedOAuth2TokenTokenUseL introspectedOAuth2TokenUsernameLisReady200ResponseStatusLisReady503ResponseErrorsLjsonPatchFromL jsonPatchOpLjsonPatchPathLjsonPatchValueLjsonWebKeyAlgLjsonWebKeyCrvL jsonWebKeyDL jsonWebKeyDpL jsonWebKeyDqL jsonWebKeyEL jsonWebKeyKLjsonWebKeyKidLjsonWebKeyKtyL jsonWebKeyNL jsonWebKeyPL jsonWebKeyQL jsonWebKeyQiLjsonWebKeyUseL jsonWebKeyXLjsonWebKeyX5cL jsonWebKeyYLjsonWebKeySetKeysL oAuth2ClientAccessTokenStrategyLoAuth2ClientAllowedCorsOriginsLoAuth2ClientAudienceL6oAuth2ClientAuthorizationCodeGrantAccessTokenLifespanL2oAuth2ClientAuthorizationCodeGrantIdTokenLifespanL7oAuth2ClientAuthorizationCodeGrantRefreshTokenLifespanL-oAuth2ClientBackchannelLogoutSessionRequiredL!oAuth2ClientBackchannelLogoutUriL6oAuth2ClientClientCredentialsGrantAccessTokenLifespanLoAuth2ClientClientIdLoAuth2ClientClientNameLoAuth2ClientClientSecretL"oAuth2ClientClientSecretExpiresAtLoAuth2ClientClientUriLoAuth2ClientContactsLoAuth2ClientCreatedAtL.oAuth2ClientFrontchannelLogoutSessionRequiredL"oAuth2ClientFrontchannelLogoutUriLoAuth2ClientGrantTypesL-oAuth2ClientImplicitGrantAccessTokenLifespanL)oAuth2ClientImplicitGrantIdTokenLifespanLoAuth2ClientJwksLoAuth2ClientJwksUriL.oAuth2ClientJwtBearerGrantAccessTokenLifespanLoAuth2ClientLogoUriLoAuth2ClientMetadataLoAuth2ClientOwnerLoAuth2ClientPolicyUriL#oAuth2ClientPostLogoutRedirectUrisLoAuth2ClientRedirectUrisL1oAuth2ClientRefreshTokenGrantAccessTokenLifespanL-oAuth2ClientRefreshTokenGrantIdTokenLifespanL2oAuth2ClientRefreshTokenGrantRefreshTokenLifespanL$oAuth2ClientRegistrationAccessTokenL"oAuth2ClientRegistrationClientUriL$oAuth2ClientRequestObjectSigningAlgLoAuth2ClientRequestUrisLoAuth2ClientResponseTypesLoAuth2ClientScopeL oAuth2ClientSectorIdentifierUriLoAuth2ClientSkipConsentLoAuth2ClientSubjectTypeL$oAuth2ClientTokenEndpointAuthMethodL(oAuth2ClientTokenEndpointAuthSigningAlgLoAuth2ClientTosUriLoAuth2ClientUpdatedAtL&oAuth2ClientUserinfoSignedResponseAlgLoAuth2ClientTokenLifespansAuthorizationCodeGrantAccessTokenLifespanLoAuth2ClientTokenLifespansAuthorizationCodeGrantIdTokenLifespanLoAuth2ClientTokenLifespansAuthorizationCodeGrantRefreshTokenLifespanLoAuth2ClientTokenLifespansClientCredentialsGrantAccessTokenLifespanL;oAuth2ClientTokenLifespansImplicitGrantAccessTokenLifespanL7oAuth2ClientTokenLifespansImplicitGrantIdTokenLifespanL