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

 

Comments

Popular posts from this blog

Why SitecoreAI - Getting into the shoes of the customer how to select right CMS

Hi Team, Lately, I have been talking to lot of our customers / potential customers and having pre-sales demos where one question always comes is "Why Sitecore" ?  Now this question can be for any product which is out for sell. And as a technician I always get into product technical features, but at the same time as a pre-sales guy, it also makes me think, surely all competitive products have same features, so definitely answer to this is not in the technicalities.  If you step back and think, we are also a customer in our daily life and buy lot of things, what is that process we go through? When we buy, how can your customer decide if this is a right fit for you or not, why we select A over B? Is it price? is it service? Is it a brand? Is it about features? Is it about brand loyalty?  When it is a technical product, I am sure it cannot start with the technicalities of the product or selecting product itself, 100% not, I feel decision is always business strategy first and ...

Hell of sitecore aliases pipeline breaking the site with 500 error

Hello Friends, I belive this blog post is very important for everyone because, It has some very serious effect on working of your headless website, i will share my experience what we faced and how we resolved it Issue we started facing Our site started giving "Key cannot be null or empty" with YSOD like following  Side affect Because of this 500 error, Our site pages were showing 500 custom error page intermittently and our MAU (Monthly Active User) drop rate increased. Sitecore KB There is already Sitecore KB article talking about this error but the patch which is provided on this link is confusing as well as very huge and it could bring other issues along with it as that upgrade patch also has lot of other things too which i did not want to introduce in our stable CMS. Known Issues - Retrieving the child items of resource items is not thread-safe Observation Though the surfaced exception was looking similar and giving same error and behavior given on this article, We looked...

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. ...