Hi everyone,
Just a small issue I’ve hit while implementing Azure AD B2C. After logging in Azure has been routing me to the base path instead of including the controller.
The solution to this turned out to be pretty straight-forward. All URLS apparently need to be including in the reply URLs of your Azure AD B2C application.
Just add a new row with the entire url to yours and it should start working immediately.
Thanks,
Chris
Hi everyone,
I’ve been mucking around with Azure AD B2C. It seems like a pretty good substitute for AWS Cognito that I’ve used previously.
While following the Microsoft sample tutorials I ran into an “unauthorized” error. A value was being returned but no access token was provided.
This seems to be indicative of an issue with scopes. In my case, I’d excluded a trailing slash on the ApiIdentifier url in the TaskWebApp web.config.
This seems to be a fairly common configuration issue. The following stackoverflow post pointed me in the right direction:
https://stackoverflow.com/a/49304044/522859
Relevant tutorial article can be found here: https://docs.microsoft.com/en-au/azure/active-directory-b2c/active-directory-b2c-tutorials-web-api?tabs=applications
Hi everyone,
I’m currently toying around with GraphQL on with HotChocolate on .NET Core Microservices. After implementing logging I ran into a bit of a problem every time I opened the GraphQL playground.
While observing my logs I noticed that an almost continuous stream of Schema logs were appearing which made it fairly difficult to track down any legitimate errors. The solution to this turned out to be fairly simple – playground offers both a polling enabled and polling frequency setting that can be configured locally:
I simply disabled this for testing, and then increased it to 30s once I’d migrated my logs to seq.
The logging implementation itself was based off the following example: https://chillicream.com/blog/2019/03/19/logging-with-hotchocolate
Thanks,
Chris
Hi everyone,
I’m currently testing out gRPC with .NET Core and hit the following error when attempting to add a timestamp field to my proto file:
My proto file was as follows:
option csharp_namespace = “publisher_api”;
package Weather;
// The weather forecast service definition
service Weather {
// Gets weather forecast
rpc Forecast(WeatherForecastRequest) returns (WeatherForecastResponse);
}
// The request message
message WeatherForecastRequest {
}
// The response message
message WeatherForecastResponse {
timestamp date = 1;
int32 temperatureC = 2;
int32 temperatureF = 3;
string summary = 4;
}
The solution was to fully qualify the timestamp namespace:
Also ensure that you’ve added the protobuff package:
See the following repo for a full example: https://github.com/Buzzology/microservicesDockerRabbitMQ
Hi everyone,
I’m currently learning microservices with .Net Core. As part of this I’ve been following one of Microsoft’s tutorials: https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial
It has all been pretty straight forward, however I hit an error when attempting to run docker build:
Updating the Dockerfile references seems to have resolved the issue. I replaced each occurrence of 2.2 with 3.0 and re-ran the following command:
My complete docker file was as follows:
FROM mcr.microsoft.com/dotnet/core/aspnet:3.0
WORKDIR /app
COPY –from=build /app .
ENTRYPOINT [“dotnet”, “myMicroservice.dll”]
Full source available here: https://github.com/Buzzology/myMicroservice
Hi everyone,
I’ve finally decided to start learning typescript while working on a side project. The plan was to convert the existing project over using the following command:
npm install --save typescript @types/node @types/react @types/react-dom @types/jest
After restarting the web server I had expected to see a tsconfig.json file that would allow me to setup my preferred configuration. Unfortunately, mine was missing.
A bit of Googling revealed that the tsconfig file isn’t actually generated until you add a .ts or .tsx file to the project. In my case, I simply renamed an existing component and the configuration file was generated during the next startup. Note that you will also have to remove your jsconfig.json file (if you haven’t already).
Thanks to this blog for the detailed info: https://blog.bitsrc.io/why-and-how-use-typescript-in-your-react-app-60e8987be8de
Hi everyone,
I’m implementing Cognito User Pools for an app and currently adding social providers (Google, Facebook, etc).
The setup process seems pretty straight forward, however the social options did not appear on my hosted ui.
It turned out that I’d missed the last step in the documentation:
– Go to “App Client Settings” (left hand menu under App integration)
– Look for “Enabled Identity Providers” and check any that you want to show
I found this a little unintuitive as I’d expected it to show once it was enabled in the “Identity Providers” section. I probably just need to learn to read ALL of the docs!
The full documentation is available here: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-social-idp.html
And the bulk of the configuration is performed here:
