GitHub – Support for password authentication was removed.

Posted on by Prahlad Dutta

While accessing the GitHub repository (Eg: git pull or git push) through git bash I was getting below error.

Username for 'https://github.com': prahlad-dutta
Password for 'https://prahlad-dutta@github.com': 
remote: Password authentication is temporarily disabled as part of a brownout. Please use a personal access token instead.
remote: Please see https://github.blog/2020-07-30-token-authentication-requirements-for-api-and-git-operations/ for more information.

To fix this issue I found the solution on the forum, here is mentioned the steps to configure the authentication token for GitHub access.

GitHub has removed support for password authentication while working with GitHub repository through git bash from 13 August 2021. Need to use access token instead. Please refer https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.

Solution

Create Personal Access Token on Github

  1. Open GitHub account.
  2. Go to Settings
  3. Click on Developer Settings
  4. Then click on Personal Access Token
  5. Click on Generate New Token button.
  6. Now fill the form and click Generate token.
  7. Now Copy the generated token.

For Windows OS

  1. Go to Credential Manager from Control Panel
  2. Click on Windows Credentials
  3. Now find git:https://github.com and click Edit
  4. Replace password with your Github Personal Access Token and save.

Reference:

https://stackoverflow.com/questions/68775869/support-for-password-authentication-was-removed-please-use-a-personal-access-to

AEM Launcher with AEM Workflow model

Posted on by Prahlad Dutta

To configure a launcher with an AEM workflow in AEM 6.5, you can follow these steps:

  1. Design the Workflow Model: Using the AEM Workflow console, design your desired workflow model. Define the steps, participants, and actions involved in the workflow. Ensure that your workflow model is complete and ready for execution.
  2. Access the Launcher Configuration: Log in to AEM and navigate to the OSGi Configuration console, which is typically available at http://localhost:4502/system/console/configMgr.
  3. Create a New Launcher: In the OSGi Configuration console, search for “Day CQ Workflow Launcher” configuration and click on it. Then, click on the “New Configuration” button to create a new launcher.
  4. Configure the Launcher: In the launcher configuration, specify the properties as follows:
    • Title: Provide a descriptive title for the launcher.
    • Path: Define the content path or resource type that will trigger the launcher. For example, “/content/mysite” or “myproject/components/page”.
    • Event Filter: Specify the event or condition that should trigger the launcher. For example, “modify”, “create”, or “delete”.
    • Workflow Model: Select the workflow model you designed in step 1 from the drop-down list.
  5. Save and Enable the Launcher: Save the launcher configuration and ensure that it is enabled by checking the “Enabled” checkbox. Click on “Save” to apply the changes.
  6. Test the Configuration: Create or modify content that meets the trigger conditions set in the launcher configuration. The launcher should detect the event or condition and automatically initiate the associated workflow.
  7. Monitor Workflow Execution: Use the AEM Workflow console to monitor the execution of workflows. Track the progress of individual workflow instances, review task assignments, and access reports on workflow execution.

Refer the video to hands on how to configure Launcher with AEM workflow

Workflow Model and AEM Launcher