Disabling OAuth authentication for the deprecated publishing framework

If you use the deprecated publishing framework, you must disable OAuth authentication, not just in the Content Deployer, but across Content Delivery. OAuth authentication must be switched on everywhere, or switched off everywhere. Note that because RWS strongly recommends against disabling OAuth, especially in a production environment, you should seriously consider switching to the new publishing framework.

Procedure

  1. In the configuration location of every Content Delivery microservice, open cd_ambient_conf.xml, the Ambient Data Framework configuration file, for editing.
  2. In each file, in the Security element, set OAuthEnabled to false, and ensure that the Rules element has an Enabled attribute set to false.
  3. Repeat until you have disabled OAuth and rules in all Content Delivery microservices.
  4. In the configuration location of every Content Delivery Java/JSP client or API, open cd_client_conf.xml, the client configuration file, for editing.
  5. In each file, comment out the TokenService element, then save and close cd_client_conf.xml.
  6. Repeat until you have commented out the Token Service element in all Content Delivery Java/JSP clients and APIs.
  7. In the configuration location of every Content Delivery .NET client or API, open Web.config, the Web application definition file, for editing.
  8. In each file, find the add element that has its key attribute set to oauth-enabled and set its value attribute to false. Then save and close Web.config.
  9. Repeat until you have commented out the Token Service element in all Content Delivery .NET clients and APIs.
  10. Restart the Discovery Service:
    1. If the Discovery Service runs as a Windows service from the Start menu, enter services.msc to open your Services screen, find the item called Tridion Discovery Service, right-click it and select Restart from the context menu.
    2. If the Discovery Service runs as a Java process, find the process (listed as Java (TM) Platform SE binary in Windows Task Manager) and restart it.
  11. Restart all other microservices, which are identifiable by the following Windows service names:
    • Tridion Content Service
    • Tridion Deployer Service
    • Tridion Session Preview Service
    • Tridion Session Content Service
    • Tridion Context Service
    • Tridion Contextual Image Delivery Service
  12. Restart all clients and APIs.