Veracode has added support for OAuth Client Credentials. Users can generate OAuth Client Credentials via the API Credentials page in the platform or via the Identity API. Although Veracode’s support for using HMAC credentials will remain intact, OAuth is a more widely adopted standard than HMAC. It also has more flexibility. For example, you can set the credential’s time to live (TTL) to an earlier expiration date, reduce (down-scope) the credential’s permissions to a subset of the user’s permissions, have more than one set of OAuth Client Credentials per user, and have more than one secret per ID to make it easier to rotate credentials before they expire. For additional information, please review the attached FAQs and go to Manage API Credentials in the Veracode documentation center. Thank you.