OAuth 2.0 and OIDC: Assessment Test Questions
- Select all correct statements about the OAuth 2.0 authorization mechanism in Acumatica ERP.
- You must register the client application in Acumatica ERP to use the OAuth 2.0 authorization mechanism.
- OAuth 2.0 can be used for OData integrations.
- With OAuth 2.0, the client application passes the username and password of an Acumatica ERP user each time the application requests data from Acumatica ERP.
- OAuth 2.0 requires an HTTPS connection between the client application and Acumatica ERP.
- Select a situation in which you must configure an Acumatica ERP website for HTTPS.
- The integration application that you are developing needs to use OAuth 2.0 authorization.
- The integration application that you are developing uses OData for data retrieval from Acumatica ERP.
- The integration application that you are developing uses the contract-based REST API.
Signing Out from Acumatica ERP
- Select all correct statements about signing out from Acumatica ERP through the contract-based REST API.
- You must always sign out from Acumatica ERP in the client application if the application uses cookies to manage the application sessions.
- You must always sign out from Acumatica ERP in the client application if the application uses the OAuth 2.0 authorization mechanism.
- The limit for the number of API users of an Acumatica ERP license does not affect the OAuth 2.0 authorization requests.
- How long can you use the access token if you have granted only the api scope to the application?
- Half an hour
- One hour
- One hour since the last REST API call
- During the current Windows session
- If you are using the contract-based REST API, how do you sign out from Acumatica ERP?
- By calling the POST HTTP method and the endpoint for signing out
- By calling the DELETE HTTP method and the endpoint for signing in
- By closing the client application
- Which interfaces contain endpoints for signing out?<ul id="_a681c668-85d2-4375-a2b5-e02044a70b25"><li>Only the contract-based REST API</li><li>Only DAC-based OData and the contract-based REST API</li><li>Only generic inquiry-based OData and the contract-based REST API</li><li>Generic inquiry-based OData, DAC-based OData, and the contract-based REST API</li></ul>[1]Which interfaces contain endpoints for signing ou.. 2025/03/2414:34:31+01:00
