You can check [1] for more details on the connection string options [1] https://docs.mongodb.com/manual/reference/connection-string/ 

What error do you see in the log files? I would recommend checking log files for any errors.

"mongodburi" was the old synatax as per my last update and a docbug needs to be logged for : https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/aem-with-mongodb.html?lang=en#mongodb-operating-system-optimizations 

First, Make sure you are using .config and not .cfg for configuration files, and the syntax was also changed from :  # org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg #MongoDB server details mongodburi=mongodb://aem:aempassword@mongodbserver1.customer.com:27000],mongodbserve...

If you go to the publish crxde, do you see the wknd pages under /content ?

The issue seems to be with the Path and Assertion consumer URL: if path: "/content/sitea" then //content/sitea/saml_login should be the ACS endpoint.If the path: "/content/siteb" then /content/siteb/saml_login should be the ACS endpoint.

Repoint does initialize before any content[1] is loaded to the repo. So, you will have to find an alternate approach to add the OOTB group to the custom group. One approach I could think of is to do it via custom code when your code initializes for the first time after AEM restart  [1] https://exper...

From what I can check internally, there are no plans for the near future. You can log a support ticket(provide business impact) for it to be prioritized with the product team.

Can you setup a DEBUG level logger on "com.day.cq.analytics.testandtarget" and try again?Share the logs once done

Change dispatcher.log to TRACE levelTrigger a request and see what is getting logged for that request.Check if the user that is used to start dispatcher has create/edit permissions on the docroot directoryCheck if the docroot directory definition is missing in the dispatcher config.