Uses of Class
co.ankatech.keymanagement.client.keymanagement.model.SuspendInternalCryptoUseCaseRequest

Packages that use SuspendInternalCryptoUseCaseRequest

Package	Description
co.ankatech.ankasecure.keymanagement
co.ankatech.keymanagement.client.keymanagement.api
co.ankatech.keymanagement.client.keymanagement.model

Uses of SuspendInternalCryptoUseCaseRequest in co.ankatech.ankasecure.keymanagement

Methods in co.ankatech.ankasecure.keymanagement with parameters of type SuspendInternalCryptoUseCaseRequest

Modifier and Type	Method	Description
InternalCryptoUseCaseResponse	InternalCryptoUseCaseOperations.suspend(UUID useCaseId, SuspendInternalCryptoUseCaseRequest request)	Suspends a use case (PATCH /tenants/{t}/internal-crypto-use-cases/{id}/suspend).

Uses of SuspendInternalCryptoUseCaseRequest in co.ankatech.keymanagement.client.keymanagement.api

Methods in co.ankatech.keymanagement.client.keymanagement.api with parameters of type SuspendInternalCryptoUseCaseRequest

Modifier and Type	Method	Description
InternalCryptoUseCaseResponse	InternalCryptoUseCasesApi.suspendInternalCryptoUseCase(UUID tenantId, UUID useCaseId, SuspendInternalCryptoUseCaseRequest suspendInternalCryptoUseCaseRequest)	Suspend an ACTIVE use case Transitions the aggregate ACTIVE → SUSPENDED and <b>cascades to the owned Cryptographic Actor</b>, which is what actually stops the workload: the actor moves to <code>SUSPENDED</code> and its signed effective-status envelope is published, so the cryptographic service answers <code>403 actor-suspended</code> on the next crypto call — including one presented with an already-issued, still-valid JWT — and the authentication service answers <code>401 invalid_client</code> for a new token request.
okhttp3.Call	InternalCryptoUseCasesApi.suspendInternalCryptoUseCaseAsync(UUID tenantId, UUID useCaseId, SuspendInternalCryptoUseCaseRequest suspendInternalCryptoUseCaseRequest, ApiCallback<InternalCryptoUseCaseResponse> _callback)	Suspend an ACTIVE use case (asynchronously) Transitions the aggregate ACTIVE → SUSPENDED and <b>cascades to the owned Cryptographic Actor</b>, which is what actually stops the workload: the actor moves to <code>SUSPENDED</code> and its signed effective-status envelope is published, so the cryptographic service answers <code>403 actor-suspended</code> on the next crypto call — including one presented with an already-issued, still-valid JWT — and the authentication service answers <code>401 invalid_client</code> for a new token request.
okhttp3.Call	InternalCryptoUseCasesApi.suspendInternalCryptoUseCaseCall(UUID tenantId, UUID useCaseId, SuspendInternalCryptoUseCaseRequest suspendInternalCryptoUseCaseRequest, ApiCallback _callback)	Build call for suspendInternalCryptoUseCase
ApiResponse<InternalCryptoUseCaseResponse>	InternalCryptoUseCasesApi.suspendInternalCryptoUseCaseWithHttpInfo(UUID tenantId, UUID useCaseId, SuspendInternalCryptoUseCaseRequest suspendInternalCryptoUseCaseRequest)	Suspend an ACTIVE use case Transitions the aggregate ACTIVE → SUSPENDED and <b>cascades to the owned Cryptographic Actor</b>, which is what actually stops the workload: the actor moves to <code>SUSPENDED</code> and its signed effective-status envelope is published, so the cryptographic service answers <code>403 actor-suspended</code> on the next crypto call — including one presented with an already-issued, still-valid JWT — and the authentication service answers <code>401 invalid_client</code> for a new token request.

Uses of SuspendInternalCryptoUseCaseRequest in co.ankatech.keymanagement.client.keymanagement.model

Methods in co.ankatech.keymanagement.client.keymanagement.model that return SuspendInternalCryptoUseCaseRequest

Modifier and Type	Method	Description
static SuspendInternalCryptoUseCaseRequest	SuspendInternalCryptoUseCaseRequest.fromJson(String jsonString)	Create an instance of SuspendInternalCryptoUseCaseRequest given an JSON string
SuspendInternalCryptoUseCaseRequest	SuspendInternalCryptoUseCaseRequest.reason(String reason)