I think now we have the solution for this. Now dispatcher also maintains a corresponding header file (*.h) to store the headers. I know it's too late to put this comment as this is a kind of basic feature everybody is aware of. Even I wasn't aware that we have this type of issue in past. But I am st...

Thanks a lot for the answer @arunpatidar. Just an update, this is true till AEM 6.4.3. After 6.4.3 this structure will be created under "/tmp/versionhistory/".

You can refer this post for the same:https://dev.to/thegreyteacher/aem-social-login-google-oauth2-23pf

You can refer this post fir OAuth integration with AEM (using AEM as an OAuth client)https://dev.to/thegreyteacher/aem-social-login-google-oauth2-23pf

This is what documentation says. But actually the path which will be used to create the user will be from the corresponding sync handler. (Also, I agree to the point that AEM automatically creates the corresponding config, but in my case I want to add it manually).

I have integrated a Google OAuth2 provider with AEM 6.5 OAuth authentication handler. There is a method named getUserFolderPath in Provider interface which should be used to get the folder path under which the user should be created. I noticed that this method is never been called and instead "user....

Thanks, it works but how did you find this? Is there anything in CFP4 release notes which confirms that this is product issue and is fixed in CFP4??

1.) Add blog function to your community site and enable the Allow Privileged members checkbox.2.) Logged in as a privileged user and create a new article and check the last field.