AEM com.adobe.granite.oauth SERVER ISSUE in aem 6.5+LTC

Hi ​@sesha_sai_Babu,

In Adobe Experience Manager 6.5, if a bundle stays in the Installed state, it usually means some required packages are missing or the version does not match. In your case, the error com.adobe.granite.auth.oauth, version=[3.12,4) cannot be resolved means AEM cannot find that package version in the runtime.

Key Points:

• Bundle in Installed state means required dependencies are not resolved.

• AEM cannot find the package com.adobe.granite.auth.oauth with the required version.

• This usually happens due to version mismatch between the project and AEM 6.5 service pack.

• Check available package versions in /system/console/depfinder or OSGi console.

• Update the Import-Package version range or align it with the version available in your AEM instance.

Once the dependency version matches, the bundle should move to the Active state.

Thanks,
Vishal

Hi ​@sesha_sai_Babu 

Your bundle is compiled against a different AEM/OAuth API version than the one actually running, so OSGi can't satisfy: Import-Package: com.adobe.granite.auth.oauth;version="[3.12,4)"

On AEM 6.5/LTS the Adobe Granite OAuth Authentication Handler (com.adobe.granite.auth.oauth) bundle exports a lower package version than 3.12, so the import range is impossible to resolve.

This mismatch usually happens when the project uses a newer uber-jar / OAuth dependency than the server's service pack. See the official OAuth bundle version mapping for 6.5 SPs in Bundle versions in Service Packs and the IMS/OAuth backport package for 6.5 in Bearer Authentication Handler backports for AEM 6.5 and 6.4.

Do this

• Align your build to the exact AEM version you run
  In your Maven POM:
  • For AEM 6.5.x on‑prem, set uber-jar (or aem-sdk-api) to the same SP level as the instance.
  • Remove any direct dependency on a newer com.adobe.granite.auth.oauth than what that SP provides.

Then run a clean build so BND regenerates Import-Package based on the correct APIs.

• Redeploy your bundle
  • Upload the rebuilt bundle/package.
  • Check /system/console/bundles — it should now move from Installed to Active.
• Only if you must pin the import manually (not recommended):
  • Open the bundle's MANIFEST.MF and relax the import to match what AEM exposes, e.g.: Import-Package: com.adobe.granite.auth.oauth;version="[3.0,4)"
  • But the better long‑term fix is step 1: never compile against a newer API than your runtime AEM.

​@sesha_sai_Babu I wanted to follow up and see if your issue has been resolved. If you were able to find a solution—either from the responses above or on your own—we’d appreciate it if you could share the details for the benefit of others. Additionally, if any reply was helpful, marking it as accepted helps future members quickly identify effective solutions. Thank you for helping improve the community experience.

Hey ​@sesha_sai_Babu 

1. First check the Felix console to confirm the exact missing packages

2. Verify your AEM instance has the latest service pack for 6.5 LTS

3. If the OAuth bundle is present but inactive, check its own dependencies

4. If you don't strictly need OAuth at runtime, use 

   resolution:=optional