Deploy to publisher causes felix config to stop working | Community
Skip to main content
T
Tom_Fought
Level 4
October 17, 2017
Solved

Deploy to publisher causes felix config to stop working

  • October 17, 2017
  • 8 replies
  • 1397 views

I have a custom saml implementation with configurations in our code base for multiple publishers. Each publisher has its own configuration.

When we deploy the saml authentication fails. If I go to the custom saml felix config and simply click the Save button, authentication starts working normally.

Any ideas why this would be happening?

Thanks

Tom

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Check the configuration of the "Apache Sling JCR Installer" in the Webconsole. Most important are in your case the "search paths" property (there should be /apps and /libs), the installation folder name regexp (".*/(install|config)$") and the Max hierarchy depth (default 4). If it's a systematic problem on all of your publishs you might override some settings there.

If that sounds ok, you need to debug the issue more systematically

* set the facility "org.apache.sling.installer.provider.jcr.impl" to DEBUG and observe the logs (use a dedicated logfile). There should be a ton of activity constantly going on.

* then add a setting and check if these DEBUG logs show any activity (they definitly should)

Jörg

8 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 17, 2017

Do you have any logs indicating a problem? If the deployment does not take effect, there should be any statements in the logs.

Jörg

VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
October 18, 2017

Jörg Hoh​

  We also have a similar kind of situation with our 6.2 servers. Any config deployed needs a restart of the server to be picked up . Some configurations , we have to go to system console and click save. We raised a daycare ticket and doesn't seem like they are able to figure out a root cause for this issue.

Thanks

Veena

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 18, 2017

Can you check if you have any nodes below /system/sling/installer/jcr/pauseInstallation ?

Jörg

T
Tom_FoughtAuthor
Level 4
October 19, 2017

There are /system/sling/installer/jcr/pauseInstallation on our publishers.

T
Tom_FoughtAuthor
Level 4
October 19, 2017

We are on 6.2 also Veena. Sorry to hear you are having this problem also.

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 19, 2017

If there are nodes within this folder, remove them. Then changes during runtime are picked up again.

Jörg

VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
October 19, 2017

While doing debug session with Day Care team, they suggested the same and we tried but there was nothing in that folder Jörg Hoh​

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 19, 2017

Check the configuration of the "Apache Sling JCR Installer" in the Webconsole. Most important are in your case the "search paths" property (there should be /apps and /libs), the installation folder name regexp (".*/(install|config)$") and the Max hierarchy depth (default 4). If it's a systematic problem on all of your publishs you might override some settings there.

If that sounds ok, you need to debug the issue more systematically

* set the facility "org.apache.sling.installer.provider.jcr.impl" to DEBUG and observe the logs (use a dedicated logfile). There should be a ton of activity constantly going on.

* then add a setting and check if these DEBUG logs show any activity (they definitly should)

Jörg

Terms & ConditionsAccessibility statement

Loading footer...