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

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

Experience Analytics not working

Hello Sitecorian, How many of you have encountered an error or the situation where graph on the experience analytics dashboard or graph on launchpad's dashboard is not working I recently encountered with this scenario where i was presented with the situation where simply graph was not coming up, Before digging completely into it and checking logs and everything, From very first high level thoughts pointed me to check Is the valid certificate is used for xconnect? Are thumbprints are correct in all configs ? We had scaled environment so i needed to check the thumbprint in all the needed roles. Is xconnect site is accessible from CD? Without any https exceptions? Is XDB is enable?  Is Tracking is enable?  Everything looked ok on first place, so i finally took my sleeves up and started digging into details, Below are the details steps and exceptions those were captured and i will also show you the topology of instances we were using. Scaled instance We are using...

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