[
https://issues.apache.org/jira/browse/JCRVLT-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
joseph jobbings updated JCRVLT-328:
-----------------------------------
Description:
vlt rcp (vault-cli-3.2.4) - used with AEM 6.4
Trying to vault rcp between remote and local AEM instances works over http but
not https.
This command (with complex password replaced with 'password') results in
correct copying of content nodes, suggesting the specified content path exists :
{code:java}
vlt rcp --recursive --batchSize 50 --update --newer
http://admin:[email protected]:4502/crx/-/jcr:root/content/foo/
http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
000001 U /content/foo
000002 - /content/foo/jcr:content
000003 U /content/foo/errors
000004 - /content/foo/errors/jcr:content
000005 U /content/foo/errors/404
000006 - /content/foo/errors/404/jcr:content
000007 U /content/foo/errors/500
000008 - /content/foo/errors/500/jcr:content
[WARN ] Error while adding node /content/foo/rep:policy (ignored):
javax.jcr.PathNotFoundException: rep:policy
// ...etc{code}
Configuring options for the JVM to use SSL and running the following command -
although /content/foo already exists on both source and destination - fails
with error "[ERROR] Error while retrieving src node /content/foo:
javax.jcr.PathNotFoundException: /content/foo"
{code:java}
export VLT_OPTS="-Djavax.net.ssl.trustStore=/Users/john/server-keystore.pkcs12
-Djavax.net.ssl.trustStorePassword=changeit
-Djavax.net.ssl.trustStoreType=pkcs12"
vlt rcp --recursive --batchSize 50 --update --newer
https://admin:[email protected]/crx/-/jcr:root/content/foo
http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
[ERROR] Error while retrieving src node /content/foo:
javax.jcr.PathNotFoundException: /content/foo
{code}
-Can vlt rcp log more verbose output for inspection/ diagnosis?- Ok, bad
question - the logging directive is clear in the documentation *--log-level
trace* etc. But I'm still puzzled as to why the command works over http but
not over https (SSL considered and allowed for)?
was:
vlt rcp (vault-cli-3.2.4) - used with AEM 6.4
Trying to vault rcp between remote and local AEM instances works over http but
not https.
This command (with complex password replaced with 'password') results in
correct copying of content nodes, suggesting the specified content path exists :
{code:java}
vlt rcp --recursive --batchSize 50 --update --newer
http://admin:[email protected]:4502/crx/-/jcr:root/content/foo/
http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
000001 U /content/foo
000002 - /content/foo/jcr:content
000003 U /content/foo/errors
000004 - /content/foo/errors/jcr:content
000005 U /content/foo/errors/404
000006 - /content/foo/errors/404/jcr:content
000007 U /content/foo/errors/500
000008 - /content/foo/errors/500/jcr:content
[WARN ] Error while adding node /content/foo/rep:policy (ignored):
javax.jcr.PathNotFoundException: rep:policy
// ...etc{code}
Configuring options for the JVM to use SSL and running the following command -
although /content/foo already exists on both source and destination - fails
with error "[ERROR] Error while retrieving src node /content/foo:
javax.jcr.PathNotFoundException: /content/foo"
{code:java}
export VLT_OPTS="-Djavax.net.ssl.trustStore=/Users/john/server-keystore.pkcs12
-Djavax.net.ssl.trustStorePassword=changeit
-Djavax.net.ssl.trustStoreType=pkcs12"
vlt rcp --recursive --batchSize 50 --update --newer
https://admin:[email protected]/crx/-/jcr:root/content/foo
http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
[ERROR] Error while retrieving src node /content/foo:
javax.jcr.PathNotFoundException: /content/foo
{code}
-Can vlt rcp log more verbose output for inspection/ diagnosis?- Ok, bad
question - the logging directive is clear in the documentation *--log-level
trace* etc. But I'm still puzzled as to why the command works over http but
not over https (SSL considered and allowed for)
> vlt rcp fails with https PathNotFoundException
> ----------------------------------------------
>
> Key: JCRVLT-328
> URL: https://issues.apache.org/jira/browse/JCRVLT-328
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Reporter: joseph jobbings
> Priority: Major
>
> vlt rcp (vault-cli-3.2.4) - used with AEM 6.4
> Trying to vault rcp between remote and local AEM instances works over http
> but not https.
> This command (with complex password replaced with 'password') results in
> correct copying of content nodes, suggesting the specified content path
> exists :
>
> {code:java}
> vlt rcp --recursive --batchSize 50 --update --newer
> http://admin:[email protected]:4502/crx/-/jcr:root/content/foo/
> http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
> 000001 U /content/foo
> 000002 - /content/foo/jcr:content
> 000003 U /content/foo/errors
> 000004 - /content/foo/errors/jcr:content
> 000005 U /content/foo/errors/404
> 000006 - /content/foo/errors/404/jcr:content
> 000007 U /content/foo/errors/500
> 000008 - /content/foo/errors/500/jcr:content
> [WARN ] Error while adding node /content/foo/rep:policy (ignored):
> javax.jcr.PathNotFoundException: rep:policy
> // ...etc{code}
>
> Configuring options for the JVM to use SSL and running the following command
> - although /content/foo already exists on both source and destination - fails
> with error "[ERROR] Error while retrieving src node /content/foo:
> javax.jcr.PathNotFoundException: /content/foo"
>
> {code:java}
> export
> VLT_OPTS="-Djavax.net.ssl.trustStore=/Users/john/server-keystore.pkcs12
> -Djavax.net.ssl.trustStorePassword=changeit
> -Djavax.net.ssl.trustStoreType=pkcs12"
> vlt rcp --recursive --batchSize 50 --update --newer
> https://admin:[email protected]/crx/-/jcr:root/content/foo
> http://admin:admin@localhost:4502/crx/-/jcr:root/content/foo
> [ERROR] Error while retrieving src node /content/foo:
> javax.jcr.PathNotFoundException: /content/foo
> {code}
>
> -Can vlt rcp log more verbose output for inspection/ diagnosis?- Ok, bad
> question - the logging directive is clear in the documentation *--log-level
> trace* etc. But I'm still puzzled as to why the command works over http but
> not over https (SSL considered and allowed for)?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
