blocks|key|3091326|text|在AEM+6.1中，服务用户必须是系统用户，这实际上意味着他们在JCR中的节点是rep:SystemUser类型。这些用户无法正常使用登录，只能通过后台进程登录。管理用户是而不是系统用户，因此您不能在这样的服务用户映射中使用管理用户。您必须创建一个新的系统用户，并为他们分配适当的权限。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3091327|如果您想阅读更多有关此更改的背景信息，请查看https://issues.apache.org/jira/browse/SLING-3854。|3091328|entityMap|0|LINK|mutability|MUTABLE|url|https://issues.apache.org/jira/browse/SLING-3854^0|1P|6|2E|1L|0|0|1Z|M|1C|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

In AEM 6.1, service users must be system users, which effectively means that their node in the JCR is of type rep:SystemUser. These users cannot be used to log in normally, only by background processes. The admin user is not a system user, so you cannot use the admin user in a service user mapping like this. You have to create a new system user and assign them the appropriate permissions.

If you would like to read more of the background on this change, take a look at <a href="https://issues.apache.org/jira/browse/SLING-3854">https://issues.apache.org/jira/browse/SLING-3854</a>.

blocks|key|2809152|text|使会议类似于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2809153|adminSession+=+resourceResolverWriter.adaptTo(Session.class);`|code-block|syntax|javascript|2809154|让会话像下面一样，希望登录异常不会发生|2809155|final+Session+session;
session=+resourceResolver.adaptTo(Session.class);|2809156|这是因为resourceResolverWriter不是隐式对象。|2809157|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

insted of making session like:

<pre><code>adminSession = resourceResolverWriter.adaptTo(Session.class);`
</code></pre>

make Session like below ,hopefully Login exception will not occur

<pre><code>final Session session;
session= resourceResolver.adaptTo(Session.class);
</code></pre>

This happen because resourceResolverWriter is not implicit object.

blocks|key|3091550|text|在贾斯汀的建议下，我试着找到了解决办法。张贴这样可以有益于其他人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3091551|目标:当用户登录时，将数据/节点写入内容(特别是/etc/userdata)。|3091552|我们可以通过两种方式来实现这一点(不管是哪种方式，用户都需要成为“系统用户”)|3091553|流程1:|offset|length|style|BOLD|3091554|步骤1:在OSGI配置中使用内置的系统用户.在OSGI中选择Apache服务用户Mapper服务|3091555|group.abc.commons-service:writeService=oauthservice+(+oauthservice是系统用户)|CODE|3091556|步骤2:为系统用户分配访问内容文件夹的权限。|3091557|​|3091558|📷|atomic|3091559|3091560|您可以看到CRX中的系统用户在：/home/users/system|3091561|流程2:|3091562|步骤1:创建一个新的系统用户。要执行此操作，请打开http://localhost:4502/crx/explorer/index.jsp|3091563|1.+Login+as+admin+
2.+Open+'User+Administration
3.+Select+'Create+System+User'
4.+Enter+"user+id"
5.+Hit+the+Green+button+(you+will+not+se+a+save+button+:)`|code-block|syntax|javascript|3091564|我已经创建了abcwriteservice用户|3091565|步骤2:转到权限，对于用户，abcwriteservice给出访问您想要写入的文件夹的权限。(在本例中：/etc/userdata+)|3091566|3091567|3091568|步骤3:打开OSGI控制台并转到Apache+User+Mapper+Service来定义服务-用户映射。|3091569|示例：group.commons-service:writeService=abcwriteservice|3091570|3091571|3091572|3091573|步骤4:在代码中，我添加了额外的参数，如：|3091574|Map<String,+Object>+param+=+new+HashMap<String,+Object>();
param.put(ResourceResolverFactory.SUBSERVICE,+"writeService");

try+{
++++resourceResolverWriter+=+factory.getServiceResourceResolver(param);

++++if+(resourceResolverWriter+==+null)
++++++++throw+new+Exception("Could+not+obtain+a+CRX+User+for+the+Service:'writeService'");

++++Node+usersRootNode+=+adminSession.getNode("/etc/userdata/users");
}|3091575|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/99b7edfdaffa838ff3deb901dfa166a9.jpg|imageAlt|1|LINK|MUTABLE|url|http://localhost:4502/crx/explorer/index.jsp|2|https://developer.qcloudimg.com/http-save/yehe-900000/2ac323694924076a60d5f36b43b5e86a.jpg|3|https://developer.qcloudimg.com/http-save/yehe-900000/8d060ff20ef392df8748943383b4dbcb.jpg^0|0|0|0|0|4|0|U|I|0|0|1F|1I|C|0|0|0|0|1|0|0|0|G|I|0|0|4|0|P|18|1|0|0|6|F|0|E|F|1G|D|0|0|1|2|0|0|G|Q|0|3|1E|0|0|0|1|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|28|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|29|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2B|8|@$H|2C|I|2D|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|2E|8|@$H|2F|I|2G|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|2H|8|@$H|2I|I|2J|J|P]|$H|2K|I|2L|J|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2M|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2N|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|2O|8|@]|9|@$H|2P|I|2Q|1|2R]]|A|$]]|$1|X|3|T|5|6|7|2S|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2T|8|@$H|2U|I|2V|J|P]]|9|@]|A|$]]|$1|10|3|11|5|6|7|2W|8|@$H|2X|I|2Y|J|K]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2Z|8|@]|9|@$H|30|I|31|1|32]]|A|$]]|$1|14|3|15|5|16|7|33|8|@]|9|@]|A|$17|18]]|$1|19|3|1A|5|6|7|34|8|@$H|35|I|36|J|K]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|37|8|@$H|38|I|39|J|K]|$H|3A|I|3B|J|P]]|9|@]|A|$]]|$1|1D|3|V|5|W|7|3C|8|@]|9|@$H|3D|I|3E|1|3F]]|A|$]]|$1|1E|3|T|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3H|8|@$H|3I|I|3J|J|K]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|3K|8|@$H|3L|I|3M|J|P]]|9|@]|A|$]]|$1|1J|3|T|5|6|7|3N|8|@]|9|@]|A|$]]|$1|1K|3|V|5|W|7|3O|8|@]|9|@$H|3P|I|3Q|1|3R]]|A|$]]|$1|1L|3|T|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|16|7|3U|8|@]|9|@]|A|$17|18]]|$1|1Q|3|-4|5|6|7|3V|8|@]|9|@]|A|$]]]|1R|$1S|$5|1T|1U|1V|A|$1W|1X|1Y|-4]]|1Z|$5|20|1U|21|A|$22|23]]|24|$5|1T|1U|1V|A|$1W|25|1Y|-4]]|26|$5|1T|1U|1V|A|$1W|27|1Y|-4]]]]

With Justin's advice, i tried and found the solution. Posting so can be beneficial for others.

Goal: To write data/nodes to content (specifically to /etc/userdata) when a user logs in.

We can achieve this in 2 ways (either way, the user needs to be a 'system user')

<h2>Process 1:</h2>

Step 1: Use in-built system user in OSGI configuration. In OSGI select Apache Sling Service User Mapper Service

<code>group.abc.commons-service:writeService=oauthservice</code> (where <code>oauthservice</code> is a system user)

Step 2: Assign that system user the permissions to access the content folder.

<img src="https://i.stack.imgur.com/q31bY.jpg" alt="enter image description here">

You see the system users in CRX at: <code>/home/users/system</code>

<h2>Process 2:</h2>

Step 1: Create a new system user. to do this
Open <a href="http://localhost:4502/crx/explorer/index.jsp" rel="nofollow noreferrer">http://localhost:4502/crx/explorer/index.jsp</a>

<pre><code>1. Login as admin 
2. Open 'User Administration
3. Select 'Create System User'
4. Enter "user id"
5. Hit the Green button (you will not se a save button :)`
</code></pre>

I have created abcwriteservice user

Step 2: Go to Permissions, and for the user abcwriteservice give Permissions to access the folder where you'd like to write. (In this example: <code>/etc/userdata</code> )
<img src="https://i.stack.imgur.com/LqpHp.jpg" alt="enter image description here">

Step 3: Open OSGI console and go to Apache Sling Service User Mapper Service to define the service-user mapping. 

Example: <code>group.commons-service:writeService=abcwriteservice</code>

<img src="https://i.stack.imgur.com/BEmD7.jpg" alt="enter image description here">

Step 4: In code, i added extra parameter, as: 

<pre class="lang-java prettyprint-override"><code>Map&lt;String, Object&gt; param = new HashMap&lt;String, Object&gt;();
param.put(ResourceResolverFactory.SUBSERVICE, "writeService");

try {
 resourceResolverWriter = factory.getServiceResourceResolver(param);

 if (resourceResolverWriter == null)
 throw new Exception("Could not obtain a CRX User for the Service:'writeService'");

 Node usersRootNode = adminSession.getNode("/etc/userdata/users");
}
</code></pre>

blocks|key|3091623|text|此外，如果您计划将来迁移到AEM+6.2，请考虑使用ACS共用以方便系统用户的创建和可用性。它消除了所有可能容易出错的手工过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3091624|https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html|offset|length|3091625|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2S|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Also, if you are planning a future migration to AEM 6.2, consider using ACS Commons to facilitate the creation and availability of system users. It eliminates all this manual process which can be error-prone.

<a href="https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html" rel="nofollow noreferrer">https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html</a>

I want to write some data to AEM, and the below code works fine for me in AEM 6.0 but not in AEM 6.1 , always throws a Login Exception as follows:

"Login Exception when obtaining a CRX User for the Service:'writeService'.org.apache.sling.api.resource.LoginException: Cannot derive user name for bundle group.tti.commons-service [395] and sub service writeService"

OSGI Config:

<img src="https://i.stack.imgur.com/gddVN.jpg" alt="enter image description here">

Code in my class:

<pre><code>import javax.jcr.Session;
import org.apache.sling.api.resource.ResourceResolver;
import org.apache.sling.api.resource.ResourceResolverFactory;
....
@Reference
private ResourceResolverFactory factory;
private ResourceResolver resourceResolverWriter;
private static Session adminSession;
...
...
Map&lt;String, Object&gt; param = new HashMap&lt;String, Object&gt;(); 
 param.put(ResourceResolverFactory.SUBSERVICE, "writeService");
try {
 resourceResolverWriter = factory.getServiceResourceResolver(param); 
 adminSession = resourceResolverWriter.adaptTo(Session.class);
...
} catch (LoginException e) {
...
}
</code></pre>

Am i missing anything on AEM 6.1?

ResourceResolverFactory getServiceResourceResolver throws Exception in AEM 6.1

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想将一些数据写入AEM，下面的代码在AEM 6.0中对我很好，但在AEM 6.1中不适用，总是抛出一个Login异常，如下所示：当为Service:'writeService'.org.apache.sling.api.resource.LoginException:获取CRX用户时，登录异常不能为bundle de...

问ResourceResolverFactory getServiceResourceResolver在AEM6.1中抛出异常
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ResourceResolverFactory getServiceResourceResolver在AEM6.1中抛出异常EN