It looks like there's something wrong with your bundle. Can you verify that you are importing the javax.jcr package and not embedding it?

Hmmm. The JCR Session interface doesn't define an invalidate() method, so I'm not sure exactly what you're referring to.If you want to programmatically log out a user from a JSP, you should do this:sling.getService(org.apache.sling.api.auth.Authenticator.class).logout(request, response);See http://d...

Can you explain why you want to do this?

If the URL you are importing requires authentication (which is likely the case if you are accessing an author server), then you need to provide the username and password in the URL, i.e. http://username:password@localhost:4502/content/dam/gsk/rssFeeds.xml 

Hi,Yes, I agree that security and personalization are different and that security must be handled on the server side. That said, passing the price via a query parameter is not really secure  so I'm sure you can understand the confusion.Justin

Hi,In AEM/CQ, personalization (whether by geolocation or referrer or anything else) is meant to be done on the client side. It sounds like your whole system needs to be reconsidered.That said, to answer your specific question, the closest thing included in the product would be http://commons.apache....

Hi Sam,I don't see any usage of the CQ Profile class. All I see is "IGProfile".Regarding the UserManagerFactory, as documented, you should use the Jackrabbit UserManager instead of the CQ UserManager (https://dev.day.com/docs/en/cq/current/javadoc/com/day/cq/security/UserManager.html). The easiest w...

Hi,I suspect the problem is that the Authorization header is being passed through from Apache to CQ. The header's value, however, is not valid as far as CQ is concerned because the username/password referenced in the header does not exist. Even when you allow anonymous access in CQ, passing a bad Au...

You need to look for a block that looks like this:<plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-scr-plugin</artifactId> <version>1.7.4</version> <executions> <execution> <id>generate-scr-descriptor</id> <goals> <goal>scr</goal> </goals> </execution> </executions> </plugin>

This was fixed in version 1.9.0 of the maven-scr-plugin. See https://issues.apache.org/jira/browse/FELIX-3568