Abstract: A first authenticator payload is obtained that includes a first authenticator random value. A first authenticator encrypted file is generated with an authenticator public key that is related to a client authenticator application. The first authenticator encrypted file is generated based on a first cryptographic algorithm. The first authenticator encrypted file includes the first authenticator payload. A first target payload is obtained that includes a first target random value. A first target encrypted file is generated with the first authenticator random value. The first target encrypted file is generated based on a second cryptographic algorithm. The first target encrypted file includes the first target payload.

Abstract: Managing client access token requests is provided. It is determined whether a current time interval between a last allowed access token request matches a regular access token request interval for a client. In response to determining that the current time interval does match the regular access token request interval for the client, a current access token request is allowed. An access token is generated for the client to access a protected resource hosted by a resource server based on allowing the current access token request. The access token is issued to the client via a network.

Abstract: A first authenticator payload is obtained that includes a first authenticator random value. A first authenticator encrypted file is generated with an authenticator public key that is related to a client authenticator application. The first authenticator encrypted file is generated based on a first cryptographic algorithm. The first authenticator encrypted file includes the first authenticator payload. A first target payload is obtained that includes a first target random value. A first target encrypted file is generated with the first authenticator random value. The first target encrypted file is generated based on a second cryptographic algorithm. The first target encrypted file includes the first target payload.

Abstract: Managing client access token requests is provided. It is determined whether a current time interval between a last allowed access token request matches a regular access token request interval for a client. In response to determining that the current time interval does match the regular access token request interval for the client, a current access token request is allowed. An access token is generated for the client to access a protected resource hosted by a resource server based on allowing the current access token request. The access token is issued to the client via a network.

Abstract: In an approach for autonomous claim requirements discovery of APIs, a processor receives an access request from a client to a server. A processor validates the access request. A processor queries claim requirements in a claim document from the server upon the validation of the access request. A processor receives the claim requirements. A processor constructs a token based on the claim requirements. A processor sends the token to the server. A processor receives a response from the server. A processor sends the response to the client.

Abstract: In an approach for autonomous claim requirements discovery of APIs, a processor receives an access request from a client to a server. A processor validates the access request. A processor queries claim requirements in a claim document from the server upon the validation of the access request. A processor receives the claim requirements. A processor constructs a token based on the claim requirements. A processor sends the token to the server. A processor receives a response from the server. A processor sends the response to the client.

Abstract: Aspects of the present disclosure relate to techniques for managing transactions, including receiving a first transaction request directed to an account of a first web application. Additionally, initiating, by a rate-limiting engine, a rate-limiting process in response to the first transaction request. The techniques further include obtaining a rate-limiting identifier, where the rate limiting identifier uniquely identifies the first web application, and where the rate-limiting identifier identifies an account owner. The techniques further include determining an alternate notification method exists for the account owner and sending a verification request to the account owner, where the verification request is sent using the alternate notification method. The techniques further include receiving a response to the verification request, performing a risk assessment, and adjusting a first security parameter in response to the risk assessment.

Abstract: Aspects of the present disclosure relate to techniques for managing transactions, including receiving a first transaction request directed to an account of a first web application. Additionally, initiating, by a rate-limiting engine, a rate-limiting process in response to the first transaction request. The techniques further include obtaining a rate-limiting identifier, where the rate limiting identifier uniquely identifies the first web application, and where the rate-limiting identifier identifies an account owner. The techniques further include determining an alternate notification method exists for the account owner and sending a verification request to the account owner, where the verification request is sent using the alternate notification method. The techniques further include receiving a response to the verification request, performing a risk assessment, and adjusting a first security parameter in response to the risk assessment.

Abstract: A computer-implemented system and method include a rate-limiting server. The server receives a request from a client and uses an early stage process to search for a rate-limiting token bucket (TB) using metadata associated with the request. Responsive to finding the TB using the first metadata, a response operation is performed. Responsive to not finding the TB using the first metadata, a late stage process is used to search for the rate-limiting TB using server-side session data associated with the request. Responsive to not finding the TB using the session data, the TB is created and associated with at least two search indexes comprising the first metadata associated with the request and the session data. Finally, the response operation is performed that comprises transmitting a determined response to the client.