OAuth 2.0 authorization code flow

The AMAccessTokenSim.scala simulation tests OAuth 2.0 authorization code flow performance. It measures the throughput and response time of an AM server performing authentication, authorization, and session token management when AM is configured to use client-based sessions, and OAuth 2.0 is configured to use client-based tokens. In this test, one transaction includes all three operations.

To run the simulation:

Make sure the userstore is provisioned, and the PingDS cache is primed.

Refer to Test user generation.
Set environment variables that specify the host on which to run the test, the number of concurrent threads to spawn when running the test, the duration of the test (in seconds), the first part of the user ID, and the user password, and the number of users for the test:
```
$ export TARGET_HOST=forgeops.example.com
$ export CONCURRENCY=100
$ export DURATION=60
$ export USER_PREFIX=user.
$ export USER_PASSWORD=T35tr0ck123
$ export USER_POOL=n-users
```
where n-users is 1000000 for a small cluster, 10000000 for a medium cluster, and 100000000 for a large cluster.
Configure AM for CTS-based sessions:
1. Log in to the Identity Platform admin UI as the amadmin user. For details, refer to AM Services.
2. Access the AM admin UI.
3. Select the top level realm.
4. Select Properties.
5. Make sure the Use Client-based Sessions option is disabled.
  
  If it’s not disabled, disable it, and then select Save Changes.
Configure AM for CTS-based OAuth2 tokens:
1. Select Realms > Top Level Realm.
2. Select Services > OAuth2 Provider.
3. Make sure the Use Client-based Access & Refresh Tokens option is disabled.
  
  If it’s not disabled, disable it, and then select Save Changes.
Change to the /path/to/forgeops/docker/gatling directory.
Run the simulation:
```
$ gradle clean; gradle gatlingRun-am.AMAccessTokenSim
```
When the simulation is complete, the name of a file containing the test results appears near the end of the output.
Open the file containing the test results in a browser to review the results.

Congratulations!

You’ve successfully run the lightweight benchmark tests on a ForgeOps deployment.