Effects of Authentication Method on Concurrency Governance
For SOAP web services that use the login and logout operations or request-level credentials for authentication, the existing governance limits per user are maintained. For web services that use token-based authentication (TBA) and for RESTlets, there are no per-user limits for concurrent requests, if the concurrency governance is enabled.
For details about different authentication types, see Authentication for SOAP Web Services.
For sessions authenticated with Outbound Single Sign-on (SuiteSignOn), concurrency is governed per user and additionally per account.
The new governance model may provide increased concurrency for web services integrations that use TBA. This change also means more limits on RESTlet integrations, which are capped at the maximum concurrency defined for an account.
If you exceed the limit for concurrent requests, an error is thrown.
- Web Services and RESTlet Concurrency Governance
- Concurrency Governance Limits Based on Service Tiers and SuiteCloud Plus Licenses
- Concurrency Governance for Internal Applications
- Account Concurrency Monitoring Resources
- Errors Related to Concurrency Violations
- Best Practices
- Retrying Failed Web Services Requests
- Sample Scenario
- Frequently Asked Questions