This doesn't necessarily means a problem. Primary and standby instances must be syncing. If there are error logs, post those and then we can look at the problem. If log size is a problem, you can change the log level for tarmk-coldstandby.log.
What is the post back URL ? If you've configured the SAML handler for intercepting the path /abc/def, the post back URL has to be /abc/def/saml_login. I've made this mistake in the past. Unfortunately this is not documented. I hope you've taken care of this.
That is strange. I've played with this 2 months back on 6.1 with no issues. Can you check if there is a random node created under this path /system/sling/installer/jcr/pauseInstallation? If this path is clean, can you try configuring ssl from the console "Apache Felix Jetty Based Http Service"
ideally you shouldn't even need a restart. the updated config should be picked up. you should see logs about jetty service restarting and then listening to the configured port. Is the server still listening to requests at the old port ?
I have come across this situation and this is what we ended up with.Have a publish server acting as your preview server. Build a workflow process to replicate assets to that preview instance. Have your preview PHP site connect that AEM preview publish instance for assets. Ask your authors/users to r...
This error suggests issue with the saml token coming in from your idp. In your config screenshot, you're configuring this handler to intercept requests made only to /saml_login and below bath. Is that intended ? Generally this path is used to register with the IDP
you can create your own traits for your custom properties. Use those traits to create your segments. Specify your client context object as the value of jsObject property for your traits.