Hi Srikanth,when you have private data like this, make sure not to cache
the page. From what you wrote, you have three levels of caching:1.
Dispatcher2. CDN3. Browser-Cachemake sure that neither layer caches the
"mypage". If neither layer caches, all requests are served by the AEM
Publish system.On the publish System you need to configure "mypage" as
not being accessible by anonymous - but only by the logged in user - use
ACLs or CUGs here.mypage then must be covered by the SAML authentication
Hi Srikanth,mAyse what you see is the result of the browsers cache. You
should see that, when you request the page with the browser‘s debug
console open (in the „network“ tab). If it comes from the browser cache
it should say something like „cached“ or “local“.Depending on the
security requirements caching in the browser might not be wanted. In
this case you would set HTTP-headers to tell the browser not to
cache.Here is an article describing how you can control
caching:Cache-Control - HTTP | MD...
Check out CRX 2.1: Improved backup – Things on a content management
systemIt is a bit older - but the basic ideas should still be applicable
to AEM6.3.Another idea - use a filesystem that supports snapshots. You
would then stop AEM, take a snapshot restart and then back up the
snapshot in the background.
I don‘t think, that you can read the SAML response in AEM directly. But
you could configure the AEM SAML Service to map a few SAML properties to
AEM user profile properties that you than can read.If you want to know
what‘s in the SAML conversation, I would use special browser plugins
(look for SAML tracer or SAML debugger in your browsers extension/plugin
store). Theses Plugins filter SAML traffic from other traffic and do the
necessary decoding for you.
Hi,the default ordering is by relevance... You don‘t have to do anything
explicitly.But „Relevance“ is a bit more elaborately calculated than
just counting the word frequency in documents. The
documentTFIDFSimilarity (Lucene 7.6.0 API)might give you a glimpse on
what is happening behind the scenes. There is also a Wikipedia article
that explains the very basicstf–idf - WikipediaWhat you have experienced
in your test case might be the normalization: Relevance is not counted
by term frequency but ...
"Client Code" not "Adobe ID" - sorry. But yes - this is the field. It
says "Client Code" but you have to enter the "Tenant ID". I didn't use
the wizard, though but created the Integration "manual" in the Cloud
Configuration. But I would assume the wizard mixes up the labels, too.
Yes we have a solution - you now have to use the "tenant id" where it
asks for the "adobe id". The tenant id is part of the URL when you open