Author Archive

May 30, 2020

Assessing your code for AEM as a Cloud Service migration

Are you interested in migrating to AEM as a Cloud Service? But, are unsure about how much time it will take or what changes you will have to do to your code to be compliant and have a working application.

In this blog, I’ll try to go over things that you should check your code for and also tools that are available to you for automating some of the changes needed to be compliant.

My recommendation would be to run the Cloud Readiness Analyzer before doing anything else and then follow this blog for further assessment. The CRA is available for download on the Adobe Software Distribution Portal

Here goes, in no particular order

Good luck migrating and see you in the cloud!

12:42 PM Permalink
January 2, 2019

AEM Rockstar 2020, we are back!

Submission window for AEM Rockstar 2020 NA is now closed.

…and just like that, we are back for another year! Join us in Las Vegas at Adobe SUMMIT 2020 for one of the most popular sessions 3 years running.

When Darin & Kaushal came up with the idea of AEMRockstar, they had one goal in mind: Give the vast AEM community a platform to show off their chops! If the last three years are any indication, the AEM Community loves AEMRockstar, and so do we!

Want to be up to date with all things AEM Rockstar?

Follow/add

Format Refresher

Below is a quick refresher on how things work.

  1. We ask that you submit your AEM (really, Adobe Experience Cloud) tips & tricks using this FORM before January 31, 2020. Submit as many ideas as you want.
  2. After submissions close, the AEMRockstar team will diligently go through each of the submissions and pick our semi finalists.
  3. We then setup a quick call with each of the semi finalist to go over their submission, let you ask questions and go over the session details.
  4. After having talked to all the semi finalists, we pick the finalists who get invited to Las Vegas to present their submission, including a live demo to the session attendees & a judging panel of Adobe heavy hitters, including last years winner, Mark Adamcin, should he choose to accept his mission.
  5. We only pay for your SUMMIT pass, but you are responsible for travel costs and handling all the fame that comes with being an AEMRockstar!

2019 Recap

  • The 2019 AEM Rockstar session was dedicated to Feike, we still miss you buddy.

  • It was the first year we held AEM Rockstar at the EMEA SUMMIT in addition to the NA SUMMIT
  • We had 85 submissions and the following individuals were selected as finalists.
    1. Mark Adamcin
    2. Ryan Dellolio & Chris Howard
    3. Dan Klco
    4. Shivangi Malot
  • Over 400 people attended the session at Adobe SUMMIT
  • Our esteemed judging panel was
    1. Jean-Michel Pittet – VP, Engineering, AEM
    2. Cedric Huesler – Director, Product Management, AEM
    3. Ruben Reusser – 2018 AEM Rockstar finalist.
  • And they chose Mark Adamcin and his submission of OakPAL as the winner. You can read more about his submission here. Mark walked away with a swanky new Glion electric scooter!
  • Survey callouts
    • Over 80% of the attendees would recommend AEMRockstar to their peers.
    • Over 82% said that it either met or exceeded their expectations.
  • Social Media highlights

#AEMRockstar Twitter Search

Tips for submission

  • AEM Rockstar 2020 Submission Guide
  • The live demos last year were a HIT! Please think about how your submission will demo
  • Submissions that cover multiple Adobe Experience Cloud offerings tend to do better with the varied audience and the judges
  • Are you solving a problem that others deal with it as well? You’d be surprised how common the problem you are facing is and how you can help the community
  • Would it make people go “WOW!”?
  • Using older tools/versions are not favored by the judges (avoid classic UI if you want to win)
  • Look at past year’s submissions and winners
  • Are you willing to open source your submission?
  • Lastly, KISS!

To be considered, all you have to do is SUBMIT your idea. We are looking for all things Adobe Experience Cloud! When you submit, please make sure you provide your complete shipping address, that ways we can send you the brand new AEMRockstar sticker. We had quite a few stickers returned last year.

The fine print

  • Adobe employees are not eligible to submit
  • You have to be willing to open source your submission before the SUMMIT session
  • The finalists are responsible for paying for their own travel and lodging. The AEMRockstar team only pays for your SUMMIT pass
  • Last year’s (2019) finalists are not eligible to submit
9:00 AM Permalink
December 17, 2018

AEM Rockstar is back for a 3rd year!

 

Submissions Closed for 2019

 

…and just like that, we are back! Join us in Las Vegas at Adobe Summit 2019 for one of the most popular sessions from 2017 & 2018.

When Darin & Kaushal came up with the idea of AEMRockstar, they had one goal in mind: Give the vast AEM community a platform to show off their chops! If the last two years are any indication, the AEM Community loves AEMRockstar, and so do we!

Want to be up to date with all things AEM Rockstar?

Follow/add

Format Refresher

Below is a quick refresher on how things work.

  1. We ask that you submit your AEM (really, Adobe Experience Cloud) tips & tricks using this FORM before January 27, 2019. Submit as many ideas as you want.
  2. After submissions close, the AEMRockstar team will diligently go through each of the submissions and pick our semi finalists.
  3. We then setup a quick call with each of the semi finalist to go over their submission, let you ask questions and go over the session details.
  4. After having talked to all the semi finalists, we pick the finalists who get invited to Las Vegas to present their submission, including a live demo to the session attendees & a judging panel of Adobe heavy hitters, including last years winner, Brett Birschbach, should he choose to accept his mission.
  5. We pay for your Summit pass, but you are responsible for travel costs and handling all the fame that comes with being an AEMRockstar!

2018 Recap

  • We had over 100+ submissions and the following individuals were selected as finalists.
    1. Brett Birschbach
    2. Bryan Williams
    3. Joost van Dun
    4. Conrad Woeltge
  • Over 300 people attended the session at Adobe Summit
  • Our esteemed judging panel was
    1. Jean-Michel Pittet – VP, Engineering, AEM
    2. Jay Dettling – VP, Partners
    3. Robert Anderson – Director, AEM Practice, ACS
    4. Dan Klco – 2017 AEMRockstar winner
  • And they chose Brett and his submission of AEM Remote Assets as the winner. You can read more about his submission here. Brett walked away with a swanky new Oculus Rift!
  • Survey callouts
    • 80% of the attendees would recommend AEMRockstar to their peers.
    • Over 88% said that it either met or exceeded their expectations.
    • 76% said that the session was excellent or above average.
  • Social Media highlights

Tips for submission

  • https://aemrockstar2019.attendease.com/submission-guide/
  • The live demos last year were a HIT! Please think about how your submission demoes.
  • Submissions that cover multiple Adobe Experience Cloud offerings tend to do better with the varied audience and the judges.
  • Are you solving a problem that others deal with it as well? You’d be surprised how common the problem you are facing is and how you can help the community
  • Would it make people go “WOW!”?
  • Using older tools/versions are not favored by the judges (avoid classic UI if you want to win)
  • Look at past year’s submissions and winners
  • Lastly, KISS!

To be considered, all you have to do is SUBMIT your idea. We are looking for all things Adobe Experience Cloud! When you submit, please make sure you provide your complete shipping address, that ways we can send you the brand new AEMRockstar sticker. We had quite a few stickers returned last year.

The fine print

  • Adobe employees are not eligible to submit.
  • The finalists are responsible for paying for their own travel and lodging. The AEMRockstar team only pays for your Summit pass.
  • Last year’s (2018) finalists are not eligible to submit.

 

Submissions Closed for 2019

5:00 AM Permalink
March 26, 2018

Integrating Microsoft Azure Active Directory OAuth with AEM. Author and publish

On a recent project we were asked to implement an OAuth integration with AEM using Microsoft Azure AD as the server and use it on both the author and publish instances.

AEM OOTB provides Facebook and Twitter OAuth providers and Cloud Service configurations. More details for AEM 6.3 can be found here.

But, since we needed the OAuth to work on the author instance as well, the Cloud Service way won’t work. Our publish use case was to disable anonymous access and only allow access via OAuth, we stayed away from using Cloud Services for publish instances as well.

Below is a list of classes we implemented

  • Scribe classes
    • Azure AD OAuth API
      • AEM uses Scribe, this class extends the scribejava DefaultApi20 class.
      • After writing this class, I submitted a PR to the scribe java project and it’s now been merged . You can use this code as reference to create the same in your AEM code base.
    • Azure AD OAuth Service
      • Also included in the PR to the scribejava project
  • Thats all for the non AEM classes, below are all the AEM related classes.
    • Azure AD Provider
    • Azure AD Login Selector
      • This class is responsible for redirecting the user to the OAuth server login page, a URL with the format similar to http://localhost:4502/j_security_check?provider=xxxxxx&configid=my-granite-oauth-configid&state=/aem/start.html
      • The Service Ranking for this class needs to be higher than the OOTB LoginSelector
      • In the requestCredentials method, you will need get the client ID and the config ID from your Granite OAuth Provider configuration. You can use the ProviderConfigManager and the ProdviderConfig classes for this.
        • for example, providerConfigManager.getProviderConfig(my-granite-oauth-configid);
      • We had to ignore some URLs for being redirected as well, for example, if the request is for below URLs, you don’t want it redirected to the OAuth login screen
        • /libs/granite/core/content/login.html
        • /libs/granite/csrf/token.json
        • /callback/j_security_check
      • This class also replaces the need for having a Cloud Service configuration, but it only works if you want every AEM request to go through this auth provider. If you have a use case similar to allowing a “Social Login”, you will need to create your own Cloud Service configuration.
      • To create a custom Cloud Service configuration, follow the docs and reference the OOTB Facebook and Twitter Cloud Service configurations to create your own.
      • Don’t forget to include the state request parameter in your redirect URI to ensure the users are redirected to the appropriate page after successful login.

On the OAuth app side, the reply URL needs to be of the format https://host:port/callback/j_securitycheck.

As always, please let me know if there are any questions.

12:44 PM Permalink
January 3, 2018

Using a JSON file with the Dropdown widget on the Metadata Schema

Have to use where you need to setup a metadata schema with a dropdown widget where the options needed to come from a JSON file? Keep on reading…

First, the JSON file.

The JSON file needs to follow the same structure as below.

{
 "options": [
 {
 "value": "en-gb",
 "text": "English-United Kingdom"
 },
 {
 "value": "en-us",
 "text": "English-United States"
 },
 {
 "value": "fr-ca",
 "text": "French-Canada"
 },
 {
 "value": "fr-fr",
 "text": "French-France"
 },
 {
 "value": "de-de",
 "text": "German-Germany"
 },
 {
 "value": "es-mx",
 "text": "Spanish-Mexico"
 },
 {
 "value": "es-es",
 "text": "Spanish-Spain"
 }
 ]
}

There needs to be an “options” array and each element in the array needs to have a “value” and a “text”. The “text” value is what is displayed to the end user and the “value” value is what is saved in JCR.

Second, where to store the file.

You can upload this file to AEM as an Asset or upload it somewhere as a nt:file. Where its uploaded will define how the widget on the metadata schema needs to be configured.

Lastly, how to configure the widget.

The dropdown widget on the metadata schema lets you define a “JSON Path” property. This property needs to point to the nt:file node of the JSON file.

What does this mean?

If you have uploaded the JSON file as an Asset, this value needs to be set to the original rendition of the asset. For example /content/dam/myproject/myfile.json/jcr:content/renditions/original. If you have upload this file as an nt:file, the path would be something like /etc/myconfigurations/myfile.json.

At the time of writing this blog, there is a known issue where if the content of the JSON file changes, you need to open the schema again and hit save for the new changes to populate. 

12:05 PM Permalink
  • Authors

  • Archives

  • Developer Resources