Skip to main content

Connecting Sitecore Content Hub to Sitecore XM Cloud

The steps to connect Sitecore Content Hub to Sitecore XM Cloud is listed out in this Walkthrough

But below are notes from my setup experience.

Prerequisites 

A. Create a service account user called “XMconnectServiceUser” (that has an email associated with it) using the doc link. You should create a password at the end of this step

B. Create an OAuth client by going to the “OAuth clients” section of the Manage admin page (gear icon in top right nav) in Content Hub. 

Name: Content Hub “Env” Connector example: Content Hub Dev Connector
Client ID: Any GUID example: 5fd3b02d-aad7-4a18-b1b9-c63a9a69fd7c
Client Secret: Any GUID example: 0b055826-c14e-44fa-b206-cff37499e229
Redirect Url: The Content Hub Url example: https://dom-d-001.sitecorecontenthub.cloud/
Client Type: Client Credentials
Users: XMconnectServiceUser

We can follow the Walkthrough for the following two sections.
1. Configure and enable the DAM connector in the XM Cloud Deploy app
2. Configure CORS for DAM


Conclusion

After the above steps are completed make sure to deploy once to the corresponding environment so the newly added variables take effect. To test go to the Pages application in XM cloud. Try to add an image to a component that takes an image. There should be a tab for Content Hub, click on it. You would get a popup window that you should use to login to Content Hub. That’s it, you should see the approved assets from content hub and be able to add them to your Pages. As long as these config variables are not deleted, the connection will continue to work. Happy XM Cloud Sitecoreing.

By

Comments

Post a Comment

Popular posts from this blog

Sitecore: Get list of logged in users

By
I had a deployment today and wanted to find a list of users who were logged into the Sitecore admin site. This was mainly so that I can contact them and let them know that a deployment was going to happen. I found the following link very useful as it gave me exactly what I was looking for. A list of users that were logged in and I contacted them. It also has the ability to Kick off users! http://{YourWebsite}/sitecore/client/Applications/LicenseOptions/KickUser Note: You can only see other users in this list if you have the right administrator permission. Logging in with a lower access level user only gave me the logged in user and no one else on the list.
Post a Comment
Read more

Create Object XML while Debugging in VS

By
 There are times when you put breakpoints in Visual studio and read object values within Visual Studio. This is all good if you are doing some debugging. But if you want to save an object like a Json object in Visual studio there isn't a straightforward way to do that. I found this piece of code that I copied and pasted in the Immediate Window in Visual Studio and was able to save the object as an XML file. (new System.Xml.Serialization.XmlSerializer(YourObject.GetType())).Serialize(new System.IO.StreamWriter(@"c:\tmp\YourObject.xml"), YourObject) Happy Sitecoreing!
Post a Comment
Read more

Updating Sitecore Image alt text

By
One of the most important conditions of making a site accessible is to make sure that all images on the site have the alt field with some value that describes the image. The simplest update we can make to Sitecore is to have the alt field automatically get the image file name. That way even if content authors forget to fill the alt field, it is pre-filled with the file name. To do this just add $name to the alt field in the standard value of an image [/sitecore/templates/System/Media/Unversioned/Image/__Standard Values] This is all good for an future images that gets uploaded to Sitecore. But what about all the existing images. For that we can write a PowerShell script (see below) to get all images in the Sitecore image folder that have empty alt tags. Export that to a csv file. $pathOfImages = "master:/sitecore/media library/MyImages" $images = Get-ChildItem -Path $pathOfImages -Language * -Recurse | Where-Object { ($_.Fields["Alt"] -ne $null) -and ($_.Fields...
Post a Comment
Read more