Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

bartek__w
bartek__w
Offline

Badges

Badges
10

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
5

Posts & Comments

Posts & Comments
13

Discussions

Discussions
0

Questions

Questions
4

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by bartek__w
Customize the badges you want to showcase on your profile
Coral UI select - empty value option - Adobe Experience Manager 06-10-2021
Hello, I found out a small issue with Coral UI Select Field and I would like to share with you in case you will find yourself in a similar situation 🙂 In my project there is a custom select field used on Asset Metadata schema which builds the Coral Select using JS API. One of the requirements was to provide one option which clears the value of that field (value is '' with label like `No value provided'). Unfortunately when I added the item using JS like $dropdown[0].items.add({ value: '', selec...

Views

195

Likes

0

Replies

1
Re: AEM 6.5 Upgrade to 6.5.7 CFP Causing Unresponsive Ins... - Adobe Experience Manager 21-07-2021
Great article, thanks ! Is this package available publicly now ?    

Views

498

Like

1

Replies

0
Re: ThreadDumps on AEM 6.3 instances - Adobe Experience Manager 21-07-2021
Hello @maryw24753203 any updates here ? 

Views

261

Likes

0

Replies

0
Re: AEM as a Cloud service - Crypto support - Adobe Experience Manager 06-05-2021
I found another documentation that states that on envs managed via Cloud Manager a special env-related variables can be used for secrets and regular configurations like. { "connection.timeout": 1000, "api-key": "$[secret:server-api-key]", "url": "$[env:server-url]" } So I far as I understand this is a way to go. On local/on prem envs used for develpmnet a shared crypto key could be used to keep all secrets safe.

Views

824

Likes

2

Replies

1
Re: AEM as a Cloud service - Crypto support - Adobe Experience Manager 04-05-2021
Hi @krishna_chaita2, thanks for the answer but I am still not sure how this should be handled on AEM as a Cloud environment. I can configure the key locally and then encrypt secrets using /system/console/crypto on my local instance and resuse this key pair on all development instances that we create manually but how that is related to the key that is used for encryption on AEM as a cloud service dev/stage/prod (I do not see option to use /system/console/crypto to get actual encrypted value). Wha...

Views

849

Like

1

Replies

0
AEM as a Cloud service - Crypto support - Adobe Experience Manager 03-05-2021
Hi, I am investigating ways of working for new AEM as a Cloud Service. One of the common features used in AEM projects was Crypo support that allowed to encrypt any secret as password, API key and keep it in the repository in OSGI config. Usually we shared one crypto key pair for our test envs and then used another keys on stg/prod. Encrypting was done manually on the instance. Could you please help me and explain how it should be done in AEM as a Cloud ? I can see that local development did not...

Views

924

Likes

0

Replies

6
Re: Using plain groovy console in vault-upgrade-hook - mi... - Adobe Experience Manager Assets 21-04-2021
Also using groovy-all package can help here, then issue with groovy-json is not showing. The only problem is to find proper version 🙂

Views

367

Likes

0

Replies

0
Re: Using plain groovy console in vault-upgrade-hook - mi... - Adobe Experience Manager Assets 15-04-2021
I found a blog post https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html that addresses the issue I had below. To fix that I added the following bundles to the instance: org.apache.sling org.apache.sling.scripting.groovy 1.2.0 org.codehaus.groovy groovy 3.0.1 org.codehaus.groovy groovy-templates 3.0.1 org.codehaus.groovy groovy-json 3.0.1 org.apache.aries.spifly org.apache.aries.spifly.dynamic.bundle 1.3.3 org.ow2.asm asm 9.1 org.ow2.asm asm-commons 9.1 org.ow2.asm...

Views

402

Like

1

Replies

2
Using plain groovy console in vault-upgrade-hook - missing requirement [groovy-json [551](R 551.0)] osgi.extender; (osgi.extender=osgi.serviceloader.registrar) - Adobe Experience Manager Assets 14-04-2021
Hi, I am trying to use vault upgrade hook with plain groovy (not groovy console) to work with latest AEM as a Cloud Service instance (local setup, I know that this will not work on AMS isntance at the moment due to issue with FileVault, for more see this link) As I read to do so I need to install Apache Sling Scripting Groovy and all it's dependencies: // https://mvnrepository.com/artifact/org.apache.sling/org.apache.sling.scripting.groovy/1.2.0 org.apache.sling org.apache.sling.scripting.groov...

Views

416

Likes

0

Replies

3
Re: Groovy console in AEM as a Cloud - Adobe Experience Manager 06-04-2021
Thanks for your response. How did you install groovy console on author ? Did you use filevault-package-maven-plugin for that with groovy all package (see snippet below)? org.cid15.aem.groovy.console aem-groovy-console-all /apps/mysite-vendor-packages/groovyconsole/install Also it seems that groovy console is not yet compatible with AEM as a Cloud see https://github.com/CID15/aem-groovy-console/issues/1

Views

1.8K

Likes

0

Replies

0
Likes given to