Hi @carmitkl ,
It seems like you're encountering a few issues during the migration process from JWT to OAuth Server-to-Server credentials for your Adobe Launch extension. Let's break down the situation:
1. Service Account (JWT) Migration: The transition from JWT to OAuth2 credentials is necessary, but the actual process of creating the package (e.g., with @adobe/reactor-packager) does not require an OAuth implementation inside the code. You only need to provide the OAuth credentials (clientId and clientSecret) during the deployment process, as you've correctly pointed out.
2. Self-Signed Certificate Error: The error Error: self-signed certificate in certificate chain seems to be more related to the certificate chain in your environment rather than the OAuth credentials themselves. This is likely an issue with your local setup, such as SSL/TLS certificate handling. You might need to ensure that your local environment trusts the necessary certificates, or there could be an issue with how your system is handling SSL/TLS connections.
3. OAuth Credentials: You mentioned filling in the credentials from the "OAuth Server-to-Server" tab. Ensure you're using the correct clientId and clientSecret for your current OAuth setup. The ones from the "Service Account (JWT)" tab may not work because JWT credentials are deprecated.
4. Further Troubleshooting: If the issue persists after ensuring your credentials are correct and your local setup is addressed, I'd suggest reaching out to Adobe Support (if your organization has access) for more targeted help. This could include checking whether any additional configuration changes are needed on Adobe's end to fully support the OAuth migration for your project.
Regards,
Amit
