XM Cloud - Publish error "Invalid Authority connection string. Required parameter 'url' is missing"

March 29, 2023 ·

XM Cloud - Publish error "Invalid Authority connection string. Required parameter 'url' is missing"

Hi Team,

If you are exploring and working on XM Cloud and have set up XM Cloud instance on your local environment, You might run into following issue on publish

 

Because Sitecore XM Cloud instance works on Experience edge and there is no content delivery server which reads from WEB DB, It always publishes on experience edge

Because we are habitual (at-least i am) to publish the API KEY after creation, Because it is mentioned in the steps below url (point-6)

https://doc.sitecore.com/xp/en/developers/hd/211/sitecore-headless-development/create-a-sitecore-api-key.html


and that is why in my other non cloud XM instance (stand alone on-prem), i am habitual to create an API and publish it, and i was doing the same in my XM Cloud Local instance too.

But with local XM Cloud docker instance, It does not work that way, Because local does not work with experience edge, and when you see publishing wizard it only has one publishing target i.e "Experience edge" and that why above error comes


so when you publish anything, It gives below exception 

#Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Sitecore.ExperienceEdge.Connector.ContentHubDelivery.Exceptions.EdgeApiException: [ExperienceEdge Publishing]: An error has occurred while publishing JobStart event 93cf8ce8-8c97-4397-9e13-5fe028ada15b for publishing job '638156301229470000'. Please see inner exception for more details. ---> Sitecore.Exceptions.ConfigurationException: Invalid Authority connection string. Required parameter 'url' is missing.

Solution

1) You actually have to do nothing, because your local rendering hosts in docker for XM Cloud, runs against CM instance, so everything should work OOTB and you do not need to publish anything as there is no content delivery role concept which reads from WEB db.

2) If you still want to publish and want to play around with any use cases etc. you can create a new publishing target called "web" and while publishing select that "web" as the target and not experience edge (not sure if this support will be there in future or not as there is no content delivery role)

everything should work !!!

I saw people asking similar questions and hence thought to pen it down


XM Cloud - Service not enabled within domain "https://auth.sitecorecloud.io"

March 16, 2023 ·

XM Cloud - Service not enabled within domain "https://auth.sitecorecloud.io"

Hi Team,

I recently have been trying to set up couple of things around XM Cloud and experience edge related things for our internal training.

I was following a documentation https://doc.sitecore.com/xmc/en/developers/xm-cloud/request-a-jwt-for-experience-edge-xm-using-oauth.html to generate the experience edge token to use GraphQL for delivery API as i wanted to query results from published version of the data i.e from experience edge

But the CURL command was always failing with above exception, i could figure out that there is something wrong with either the URL or connecting to it, but as everything else was working fine i thought either the format of the URL is wrong or something with it.

See the documentation i refereed (it was not updated at that time, right now it is updated correctly and working fine)

 

I knew that there are same kind of documentation exists for XM and XM Cloud, but their URLs are different, so i tried to double check with simple XM documentation, because i know token generation process is same, with my surprise, over there documentation was showing a different value for "audience" URL  

So, now i had some findings, so i tried with the different URL given on XM documentation and it worked and generated the token, the URL was https://api.sitecorecloud.io instead of https://auth.sitecorecloud.io

To double check this behavior, i created a Sitecore ticket case no CS0359842 and verified this scenario with them,

SC have acknowledged that The correct audience URL is https://api.sitecorecloud.io and not https://auth.sitecorecloud.io also they mentioned. and promised to update the documentation, Currently the documentation is updated fine and reflecting the correct URL.


 and CURL command is working just fine too without any issue

 

My first Sitecore MVP award

March 10, 2023 ·

My first Sitecore MVP award

Hello Sitecorians & technician around the world !!!

I had my learning and sharing activities in pipeline for this year and before i start them i just wanted to make sure i take out this blog first and share about my experience and journey of being MVP and thank the community too and my team mates who helped me along the way, and express my gratitude.


This is purely to help and encourage other members of the community, and explain them that i am no exception but there are steps, and rules, few check points, if you follow them, you can also become MVP.

WHY

One of the question or the overall mood i have observed is why MVP? So question is actually not about becoming MVP, It's not even about being Sitecore expert , but questions is about sharing as much as we know and learn, if you already are working on Sitecore, You know how much is happening in that zone, Things are changing at rapid pace, so if you are already working in that technology and already know things and modifications that you do and different bugs that you resolve, why don't just share them? 

Forget about becoming MVP, just try help community and share as much as you can about your learning, you point of views and create content out of it, real time bugs, your experience, technical solution,Sitecore tickets that you created, all these are catalyst of becoming your MVP, and i am sure if you work in Sitecore, you must already be doing all these, so you are already entitled to apply for MVP and can become MVP.

I will not write much about benefits of becoming MVP, as there is enough material out there and a good one is MVP Benefit but i would definitely write points using which other developer can relate with it, as i have had the same journey too, you can do that too 

I wanted to share my Sitecore MVP journey, and just want to motivate others and give some pointers which i followed personally and using which i think i was able to make it to MVP

1) Write when it's fresh in your mind 

Generally, In our day to day life, we see bugs, we see things which are modifiable, so any of those points which you think that other people will face or must have faced, you can create content about it or blog or share it on the social channels.

The best way which have worked for me is, the moment i see that this can be a potential bug, content opportunity, i quickly make a draft of 2-3 lines of high level pointers which i was looking into it and using which i resolved the bug or did some functionality, because you can write with 100% efficiency when its fresh in your mind, if you wait for another week or a weekend, it could be possible that you already have forgotten about it, so because in day to day life it becomes difficult to take out time, make sure you just quickly make a draft, and later on you can articulate an article on a weekend over a coffee :) 

2) Look for every opportunity, keep eyes and ears open

Normally, we tend to forget things one we have resolved, but to get your material and a good content, you will have to keep your eyes and ears open, Because most of the blog content or webinar content or any technical learning content will come from your day to day work only and if you ignore them then you will be ignoring a lot of good material, so always make sure you note them down and use it further to write an article or share it on a social media.

3) Self discipline & Self motivation

It is all about making sure you commit to the plan, Because its a year long process, You will have to make sure that you keep that motivation going, and it's very easy to loose that rhythm or the momentum if you do not keep yourself motivated, Make sure every month you contribute or at least make sure to keep your drafts and do not miss out on it, Otherwise down the line there will be too much at once and you will feel overwhelmed, Instead as i said, keep drafting offline couple of lines and do a full fledged article writing on a weekend or a free day, You can join hands with local developers or communities to keep yourselves motivated.

4) Plan activities of the year

To make sure that you have a plan and you can work on it, having a plan is a good way to gauge your progress and plan things in more efficient way, Make sure you maintain a good balance among writing blogs, webinars, helping community by answering their questions etc. because you have to have contribution in those categories, Below are those categories

  •     Blogs - Write articles and share them
  •     Webinars - Schedule sessions with user groups
  •     Slack channels - There are lot of slack channels which you can join and answer queries
  •     Sitecore Stack Exchange -  Answer queries on stack exchange.
  •     Social channels - LinkedIn, Twitter, Promote Sitecore, like and share
  •     Help community in offline channels - If you are working for some organization then you can        do local webinars or take part in training, be a solution provider and help team in learning              Sitecore and new technologies around Sitecore.

5) Don't target to become MVP, But target to share more, care more, help community authentically

If i take my example, i have been blogging before i was working in Sitecore, so i always had intention to share things which i thought is new or could be helpful for others and if i can help others by any means i would always want to do that, so that is my inspiration comes from there where i feel, If i put something on internet and if its saving someone else's time and if its helping them resolve their blockers then i would go and do it

Now, I work in Sitecore, but intention is same, so i keep sharing and keep updating myself and at the same time i keep sharing things and plan to do webinars etc. in that way MVP becomes the bi-product of your efforts, Even if MVP does not happen, you never tried for it, but you tried to share things and that should be the intentions, and MVP will be cherry on the top of cake for the efforts you did put into it.

I love this quote "You Miss 100% Of The Shots You Don't Take.' You Need To Start Shooting"

6) Do your karma

Similar to point-5, You just have to do your bit and rest will fall in place, keep putting your efforts and be consistent / persistent / authentic / honest in your efforts.

"If you light a lamp for someone else, It will also brighten your path.", Just keep doing your bit.

7) Note down your contributions

Over the year, There will be times where you have contributed directly or indirectly to Sitecore ecosystem, but note down those points somewhere handy, because you can mention those points while filling up your MVP application on the day of submission.

It will be difficult to recall smallest contribution, major contributions are fine and those are blogs, webinars, and you can remember those and mention those, but  there will be times where you have attended events, marketed Sitecore, took part in surveys, took part in any Sitecore training as trainer, and what not. all these you can still mention but you can do it easily if you have drafted them somewhere 

7) Sell yourself and your hard work when you fill the form and be authentic about it

Personally, What i feel is, if you have worked hard over a year and if you do not draft your final MVP application properly, it will be injustice to your hard work, so fill the application very calmly and don't miss out on any points of contributions you did over the last year.

I hope, as a reader and as a Sitecore enthusiast, it will make sense and help you relate your journey and plan and encourage you to try for MVP this year.

Thank you

MVP is something very personal generally, you do it, you put efforts and you get it (Or don't get it), but i would like to thank Horizontal Digital for always encouraging the team to prepare, take part and facilitate so that they have opportunities to explore things, I would also like to thank Khushboo Sorthiya for her talks and guidance whenever needed, and Nikki Fulp to promote my work and creating a buzz.