The application relates in particular to a method for authentication of a secure electronic device (BNK_SRV) from a non-secured electronic device (PC, SP) comprising an input peripheral (KBD, MS, TS, CAM), an output peripheral (SCR, SPK, PRN) and a secure electronic circuit (TPM). The application also relates to a secure electronic circuit (TPM), a computer program and a storage medium arranged to implement such a method.

A method and system for reducing triggering of throughput penalties imposed on a group of users by a software-as-a-service (SaaS) server due to Application Programming Interface (API) calls exceeding limits of the SaaS server. The approaches include intercepting requests to the SaaS server from a user group and monitoring both a rate of API calls for the requests and a rate of API events generated by forwarding the API calls to the SaaS server, intercepting the SaaS server's responses, where some of the responses indicate a throughput penalty imposed by the server, identifying one or more power users from the user group based on the rate of generated notifications, and throttling the rate of the API calls for the requests submitted by the identified power users of the user group to the SaaS server in accordance with an API call throttle limit, thus reducing triggering of the throughput penalty.

A method and system disclosed dynamically throttling a rate or volume in time of a power user for avoiding throughput penalties imposed by SaaS vendors on a user group due to excessive Application Programming Interface (API) events from users in the group, monitoring API event rate for requests from the group, collectively, and from individual users of the user group to a SaaS vendor is disclosed. Also, identifying a power user as submitting API events in excess of a limit, and on behalf of the user, throttling the power user's rate of API events submissions, based on a configurable policy specific to the SaaS vendor managed by a proxy, to reduce the user's impact on the API event rate of the group at least when the group's API rate, overall, exceeds or approaches a SaaS imposed trigger of a throughput penalty on the group, thereby avoiding triggering of the throughput penalty by the SaaS.

A method and system for reducing triggering of throughput penalties imposed on a group of users by a software-as-a-service (SaaS) server due to Application Programming Interface (API) calls exceeding limits of the SaaS server is disclosed. The approaches include actions of intercepting requests to the SaaS server from a user group and monitoring both a rate of API calls for the requests and a rate of API events generated by forwarding the API calls to the SaaS server, intercepting the SaaS server's responses, where some of the responses indicate a throughput penalty imposed by the server, inferring load conditions of the SaaS server by analyzing the varying rate of API events against the responses with imposition of throughput penalty and setting an API call throttle limit dynamically adaptive to the inferred load conditions, then throttling the rate of the API calls for the group's requests according to the throttle limit.

A method and system for reducing triggering of throughput penalties imposed on a group of users by a software-as-a-service (SaaS) server due to Application Programming Interface (API) calls exceeding limits of the SaaS server is disclosed. The approaches include actions of intercepting requests to the SaaS server from a user group and monitoring both a rate of API calls for the requests and a rate of API events generated by forwarding the API calls to the SaaS server, intercepting the SaaS server's responses, where some of the responses indicate a throughput penalty imposed by the server, inferring load conditions of the SaaS server by analyzing the varying rate of API events against the responses with imposition of throughput penalty and setting an API call throttle limit dynamically adaptive to the inferred load conditions, then throttling the rate of the API calls for the group's requests according to the throttle limit.

A method of avoiding throughput penalties imposed by SaaS vendors on a user group due to excessive API events from users in the group, monitoring API event rate or volume in time for requests from the group, collectively, and from individual users in the user group to a SaaS vendor is disclosed. Also, recognizing a power user as submitting API events in excess of a limit and taking action to reduce the user's impact on the API event rate of the group when the API rate for the group, overall, exceeds or approaches a SaaS imposed trigger of a throughput penalty on the group. Further included is rationing transmittal of API event submissions from the power user to the SaaS and avoiding triggering of the throughput penalty by the SaaS, reducing latency for the users in the group other than the power user and increasing latency for the power user.

A method and system disclosed dynamically throttling a rate or volume in time of a power user for avoiding throughput penalties imposed by SaaS vendors on a user group due to excessive Application Programming Interface (API) events from users in the group, monitoring API event rate for requests from the group, collectively, and from individual users of the user group to a SaaS vendor is disclosed. Also, identifying a power user as submitting API events in excess of a limit, and on behalf of the user, throttling the power user's rate of API events submissions, based on a configurable policy specific to the SaaS vendor managed by a proxy, to reduce the user's impact on the API event rate of the group at least when the group's API rate, overall, exceeds or approaches a SaaS imposed trigger of a throughput penalty on the group, thereby avoiding triggering of the throughput penalty by the SaaS.

A method and system for reducing triggering of throughput penalties imposed on a group of users by a software-as-a-service (SaaS) server due to Application Programming Interface (API) calls exceeding limits of the SaaS server. The approaches include intercepting requests to the SaaS server from a user group and monitoring both a rate of API calls for the requests and a rate of API events generated by forwarding the API calls to the SaaS server, intercepting the SaaS server's responses, where some of the responses indicate a throughput penalty imposed by the server, identifying one or more power users from the user group based on the rate of generated notifications, and throttling the rate of the API calls for the requests submitted by the identified power users of the user group to the SaaS server in accordance with an API call throttle limit, thus reducing triggering of the throughput penalty.