This AEMCS-API-Client-Lib uses JWT authentication, which is deprecated, and about aemcs-api-client-lib HOT 1 OPEN

AEMCS has a AEM-CS Environment specific developer console called AEM Dev Console. This issues JWT credentials in yaml from. This code was written as sample/example code for how to process those yaml files and use them to get an IMS Access Token. JWT Credentials (public and private key etc in the yaml files) is not going to be depreciated at this time. If that changes will will make an announcement.

The Adobe Developer Console (ie not specific to AEM-CS) is deprecating IMS JWT Credentials in favour of a simpler OAuth Server to Server credential. We could provide examples of how to exchange the OAuth Server to Server Credentials in this code, and we almost certainly will do that if AEM Dev Console adds OAuth Server to Server Credentials. However I think this is unlikely since many of the AEM-CS API are being reworked and improved on and will be available from Adobe Developer Console.

I guess it comes down to a question: How much is example code needed in this git repo for OAuth Sever to Server vs that code being available elsewhere. IIRC, OAuth Server to Server is really simple. A single GET to the right API returns the IMS Access Token. No JWT creation or signing is required.

wdyt ?

from aemcs-api-client-lib.