I believe you need to add that jar to the OSGI console in order to use the services associated with that jar file.You can include any jar within AEM as long as it is able to resolve the imported/exported bundle list mentioned in the metadata of that jar file

Seems like a config mismatch between AEM and IDP. Check the following:Check if ds:signature is part of SAML assertion > If not, This is to be done on IDP end and check the checkbox for signed AssertionCheck for nameId format in SAML response, The format should exactly match the nameId Policy format ...

Looks like something is wrong at "/conf/site/settings/wcm/templates/content-page/policies/_jcr_content.1326118631670.json ". Try to remove this policy node and recreate it.

Arun,Yes, you are right. the path variable and the Post back URL should match. In other words, if path variable is set to "/content", IDP should be posting back to <HOST>/content/saml_login"Setting postback URL to "sites.html" or "assets.html" won't work.

Can you check if CSRF settings are correct on dispatcher[1]Also make sure POST request to */saml_login is allowed[1] Configuring Dispatcher to Prevent CSRF Attacks

Setup a DEBUG logger on "org.apache.sling.caconfig.resource" to get more info on this error.

You are probably missing one of the sync config. Check [1] for more details and answers to your questions.[1] Configuring LDAP with AEM 6

Hi Arun,AEM will only process the IDP response if the SAML response is posted to "saml_login" path.Make sure IDP is posting the SAML response to <HOST>/saml_login if path value is set to "/" and <HOST>/content/saml_login if path value is set to "/content"

AEM 6.4 with open JDK is not officially supported and not recommended by Adobe

What is the AEM version?Check if all bundles are in active state?What is the error observed in the error.log when you try to access login page ?