Skip to main content

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

 

Labels:

Comments

Post a Comment

Popular posts from this blog

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...
9 comments
Read more

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...
2 comments
Read more