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

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right? Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging 1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for Leprechaun and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1) In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!

Daivagna Nanavati

Search This Blog