Hi all
Recently upgraded form 6.1 to 6.3. AEM version 6.3.1. All bundles active.
On start up error.log has the below error messages. I do not know how this is affecting my instance. Anyone know how to resolve this?
Is it related to the social login/plugin known issue? I am getting errors related to social login. This is despite having installed service pack 6.3.1. I thought the issue would be resolved with the service pack.
14.11.2017 12:32:47.536 *INFO* [FelixStartLevel] com.adobe.granite.auth.oauth.impl.OAuthManagerImpl creating OAuthManagerImpl
14.11.2017 12:32:47.536 *INFO* [FelixStartLevel] com.adobe.granite.auth.oauth.impl.OAuthManagerImpl activating OAuthManagerImpl
14.11.2017 12:32:47.537 *INFO* [FelixStartLevel] org.apache.sling.servlets.resolver Service [ServletResourceProvider for Servlets at [/libs/foundation/components/primary/social/oauth/accesstoken/GET.servlet],5156, [org.apache.sling.spi.resource.provider.ResourceProvider]] ServiceEvent REGISTERED
14.11.2017 12:32:47.538 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[com.adobe.granite.auth.oauth.provider])] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,10, [org.osgi.service.cm.ConfigurationAdmin]] [org.osgi.service.cm.ManagedServiceFactory, id=5155, bundle=149/launchpad:resources/install/0/com.adobe.granite.auth.oauth-1.0.44.jar]: Updating property oauth.config.id of configuration com.adobe.granite.auth.oauth.provider.9035b323-0c12-4e17-aa3f-857f3ae96613 caused a problem: Config Id must be unique. (org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.)
org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.
at com.adobe.granite.auth.oauth.impl.helper.ProviderConfigManagerBase$ProviderConfigService.updated(ProviderConfigManagerBase.java:121)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1431)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1373)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105)
at java.lang.Thread.run(Unknown Source)
14.11.2017 12:32:47.540 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[com.adobe.granite.auth.oauth.provider])] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,10, [org.osgi.service.cm.ConfigurationAdmin]] [org.osgi.service.cm.ManagedServiceFactory, id=5155, bundle=149/launchpad:resources/install/0/com.adobe.granite.auth.oauth-1.0.44.jar]: Updating property oauth.config.id of configuration com.adobe.granite.auth.oauth.provider.6941d590-ab33-479b-a723-6427b9c27f7a caused a problem: Config Id must be unique. (org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.)
org.osgi.service.cm.ConfigurationException: oauth.config.id : Config Id must be unique.
at com.adobe.granite.auth.oauth.impl.helper.ProviderConfigManagerBase$ProviderConfigService.updated(ProviderConfigManagerBase.java:121)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1431)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1373)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105)
at java.lang.Thread.run(Unknown Source
Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
This was resolved by removing duplicate entries for the configuration com.adobe.granite.auth.oauth.provider
The social plugin login exception is due to bad/missing configuration.
Views
Replies
Total Likes
This was resolved by removing duplicate entries for the configuration com.adobe.granite.auth.oauth.provider
The social plugin login exception is due to bad/missing configuration.
Views
Replies
Total Likes
Views
Likes
Replies