autogen(openapi): regenerate swagger spec and internal client

[skip ci]
ory · Jan 16, 2025 · a21cec7 · a21cec7
1 parent 4b137fd
commit a21cec7
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 2 deletions.
diff --git a/internal/httpclient/api/openapi.yaml b/internal/httpclient/api/openapi.yaml
@@ -1152,6 +1152,8 @@ paths:
 
         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.
+
+        If the login session was issued by a login provider, the login provider is asked to invalidate its session as well.
       operationId: revokeOAuth2LoginSessions
       parameters:
       - description: |-

diff --git a/internal/httpclient/api_o_auth2.go b/internal/httpclient/api_o_auth2.go
diff --git a/spec/api.json b/spec/api.json
@@ -3011,7 +3011,7 @@
     },
     "/admin/oauth2/auth/sessions/login": {
       "delete": {
-        "description": "This endpoint invalidates authentication sessions. After revoking the authentication session(s), the subject\nhas to re-authenticate at the Ory OAuth2 Provider. This endpoint does not invalidate any tokens.\n\nIf you send the subject in a query param, all authentication sessions that belong to that subject are revoked.\nNo OpenID Connect Front- or Back-channel logout is performed in this case.\n\nAlternatively, you can send a SessionID via `sid` query param, in which case, only the session that is connected\nto that SessionID is revoked. OpenID Connect Back-channel logout is performed in this case.",
+        "description": "This endpoint invalidates authentication sessions. After revoking the authentication session(s), the subject\nhas to re-authenticate at the Ory OAuth2 Provider. This endpoint does not invalidate any tokens.\n\nIf you send the subject in a query param, all authentication sessions that belong to that subject are revoked.\nNo OpenID Connect Front- or Back-channel logout is performed in this case.\n\nAlternatively, you can send a SessionID via `sid` query param, in which case, only the session that is connected\nto that SessionID is revoked. OpenID Connect Back-channel logout is performed in this case.\n\nIf the login session was issued by a login provider, the login provider is asked to invalidate its session as well.",
         "operationId": "revokeOAuth2LoginSessions",
         "parameters": [
           {

diff --git a/spec/swagger.json b/spec/swagger.json
@@ -1280,7 +1280,7 @@
     },
     "/admin/oauth2/auth/sessions/login": {
       "delete": {
-        "description": "This endpoint invalidates authentication sessions. After revoking the authentication session(s), the subject\nhas to re-authenticate at the Ory OAuth2 Provider. This endpoint does not invalidate any tokens.\n\nIf you send the subject in a query param, all authentication sessions that belong to that subject are revoked.\nNo OpenID Connect Front- or Back-channel logout is performed in this case.\n\nAlternatively, you can send a SessionID via `sid` query param, in which case, only the session that is connected\nto that SessionID is revoked. OpenID Connect Back-channel logout is performed in this case.",
+        "description": "This endpoint invalidates authentication sessions. After revoking the authentication session(s), the subject\nhas to re-authenticate at the Ory OAuth2 Provider. This endpoint does not invalidate any tokens.\n\nIf you send the subject in a query param, all authentication sessions that belong to that subject are revoked.\nNo OpenID Connect Front- or Back-channel logout is performed in this case.\n\nAlternatively, you can send a SessionID via `sid` query param, in which case, only the session that is connected\nto that SessionID is revoked. OpenID Connect Back-channel logout is performed in this case.\n\nIf the login session was issued by a login provider, the login provider is asked to invalidate its session as well.",
         "consumes": [
           "application/json"
         ],