The introduction of Tridion Access Management in Tridion 9.5 has changed the way you need to create a core service client. Spoiler alert: it has become a lot more complicated, especially if you need a session-aware client.
In this blogpost I will take you through the steps.
It can be very useful to set the log level of Tridion’s content service to Debug every once in a while. I admit I always do that on my own development environments – you never know when you will need it. Of course, I would not recommend it for production environments but that’s another story.
One thing is really annoying though: every 10 seconds, the content service makes a call to the discovery service (for whatever reason, perhaps to check the validadity of the tokens or something). And this leads to so much logging that you always have to wade through endless lines of useless logging before you get to the interesting bits.
Today, version 2.6 of DD4T.Model was released. It contains bug fixes and security patches. Most important changes:
Welcome to the first blog post of 2021! (funny enough also my first blog post)
Recently while trying to work on a direct integration between a React Single Page Application and the GraphQL endpoint of the microservice, I encountered the following errors in the React application:
