Transcript

Note: The following is the transcription of the video produced by an automated transcription system.

Hey, guys, this is Akshay Sura today will be looking into content hub digital asset management integration into our Sitecore CMS. This is by far the easiest integration I’ve seen so far. It was really straightforward and easy. Hope this makes it easier for you. Next, we need to download the Sitecore Connect for Sitecore DAM. I am using Sitecore 9.3 And the Content Hub version is 3.3.4, it’s compatible with SXA after 1.9 onward. So, get your content hub. So here we would need to configure the authorization part of it so get into settings. Once you get into settings, choose the portal configuration and CORS configuration. Here you are going to pass the URL of your Sitecore instance, this is my test instance. Go ahead and add it once that’s done go ahead and save. And then we would need to go to your authentication part of it, change the mode to text, it’s a little bit easier and then change the auth mode from active to passive code and save. So, this finishes all the things we need to do from a content hub perspective. Next, let’s get to our Sitecore instance, go to control panel, we want to install the package, the DAM connect package. So, go ahead and choose the package, which I already had put it on the instance. Once you select that, install it. If you get an override warning, override everything once the once it’s installing, just reset your instance and let it come back. Once instance comes back, go into I usually the old habits I go to desktop, open up content editor.

What we’ll be doing is we want to go set up the settings for this are going to system modules, DAM, config and DAM connecter here. We need to specify that our instance name and then the search page. So let’s get back to our content hub of instant so that our content hub of instance’s URL and then you basically append site dam connect and approved assets to that URL that’s your URL use for the search page on our Sitecore Instance. And so basically copy paste those, make sure the values are correct. I haven’t touched anything else so I’m just going to go ahead and save. Once that’s done, open your web config because now we have to modify the content security policy to append a couple of your URLs to the end of it. So, let me just show you what I, um. It’s all documented so you can look at the documentation. But essentially, we have to do the child source and the connect source, both pointing to your content hub instance. And so, these two values would need to get appended to the end of your existing value inside of the Web config. Go ahead, save it. And then once we save that, let’s get back to the instance, refresh it so we can reload that. Once it comes back, get back into the content editor. Let’s go to the home node and then show editor here. We want to go ahead and hit the DAM media icon.

And then at first you might get a popup warning the first time you open it. So, go ahead and unblock the pop ups. And once you do that, go ahead and close this guy, reopen it so that it opens up the pop up. It’s looking for basically wants to authenticate. I have an Okta log in for the SPN and the and developing it for the network. So, go ahead and provide your network credentials depending on which ones you have. And then once you sign in, you will be able to see all your approved assets from your content hub instance pretty seamless. This is one of the easiest integrations I’ve done. So, you can look at the preview for a thing. You could do quite a few things in here, but let’s just go ahead and select one of the assets. Basically, you need a public URL for this. So, by default, I’m just going to go ahead and hit save without changing any attributes. You could change different attributes for every different set. You get a different public URL, this one I just selected whatever was the default. So once the public link is created, just go ahead and select that, accept it, save this piece of content, go ahead and publish that. And then all you need to do is open up an Incognito browser and then let’s take a look what happens on that page. So, let’s load it up once the page loads inspect that image and you can see that it’s pointing to our content hub instance. And so, it’s very simple. Like I said, it’s one of the easiest integrations I’ve done. Again, if you have any questions, you can always reach us through public channels. Follow us on LinkedIn and Twitter and on YouTube. We’ll be following this up with a PCM videos coming up shortly.

If you have any questions, please get in touch with me. @akshaysura13 on twitter or on Slack.

Follow us on Twitter Follow us on LinkedIn Follow us on YouTube