dbdigital04: where exactly did you implemented this change in the
service? Also, we are facing this issue for
jcrinstall:/apps/install/aem.parent,core-x.y.z.jarWe are using
to invalidate cache and this configuration somehow gets binded to an old
The API call  you mentioned is not recommended to be used for the use
case you are after.The call  gets bound to the bundle performing the
call (the scripting bundle in this case).So, you have two optionsUse
getConfiguration(configName, null) - this way you're only getting the
configuration without binding it. However, this call will create the
configuration if it doesn't exist, which is not what you want (I assume
!).Therefore, use ConfigurationAdmin.listConfiguations instead for a
This is not acceptable advice, even less so coming from Adobe staff!
It's explicitly stated time and time again NOT to modify anything under
/libs. This file was overwritten during a recent SP2 upgrade. Please
Hi Guys,First of all thanks to all of you who tried to hep me with this
problem.I think I now better understand this problem. As Abhishek
mentioned if we configure root path ("/") it works because the
/system/sling/logout servlet redirects the response to "/" after logout.
If root path is not there in SAML config path then after logout
(Autheticator logout -
AEM login process will kick in. If we have "/" configured then ...
Hi Chetan and Sham,I am facing the exactly same problem. May I know what
did you do to resolve the issue. I have configured the following path in
SAML config/saml_login/content/myAppAuto create is trueGroup Memebership
is BlankDefault Group is "TestGroup" (Exist in AEM)If I create the user
in AEM works fine. ---> We have a problem over here, if the user exist
in IDP and doesn't exist in AEM then requests go into infinite loop. Is
there a solution to this problem?If user doesn't exist in AEM (Aut...
Hi Deepak,Thank you for reaching out to Adobe Community.You might want
to spent some time on the Adaptive Forms documentation here and see if