For SSO follow below https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/single-sign-on.html Also I have tried saml in one of project using below link. it workds toohttps://helpx.adobe.com/experience-manager/using/aem63_saml.html   

I have got similar issue. I have reindexed all OOTB indexes and setting reindex flag = true , then this issue got resolved.

remove the mandatory validation on that field, Then it will start working.

Try with below query type=cq:PageContentpath=/content/retailgroup.property=cq:lastmodifiedbygroup.property.1_value=value1group.property.2_value=value2group.property.3_value=value3group.property.operation=unequalsgroup.property.orp.limit=-1p.hits=full

You can write a servlet. , which can consume the API end point and parse the entire json and then for each product it can create a node in the JCR using various API. It would be great if you share more details on how you want to create a product component.  Note: Rather create one node per product ,...

Translation of Binary will be an additional Add on for any translation services. Default service will not support Binary translations.

There are multiple ways 1) option1 : If you dont want acticate option , simply handle it via ACL by removing replicate access.2) Option2: If you want the button to be shown, then overlay the libs/* node corresponding to libs and then write custom js to handle this. Custom js can directly call a serv...

There is no OOTB way. Only option is to customize. 

404 can occur at one of the 3 levels1) CDN2) Apache(Dispatcher)3) AEM Publish Do check , first at which level it is occurring and then it would be easy to debug. In case of AEM , you need to check for custom 404 handling.

No matter whatever you do , very difficult to get rid of this issue. If its lower environment or local instance create a fresh instance and reinstall the content and code. If its production you can follow the process to recover. I am suggesting to recreate the instance for Lower and local environmen...