Oops, Bazar should work now (still BETA)

Sorry, the last release had wrong versioning of some helper slots libraries, and the Bazar didn't work as a consequence. This should work now. Notice, the Bazar is an experimental component, and not entirely done yet - But at least it's a taste of what's to come.

Bazar (BETA)

This release features a minimalistic Bazar based upon GitHub's infrastructure, allowing you to fill your Magic backend with micro services similarly to how you'd install apps on an iPhone or Android. Warning, this is not 100% stabilised yet, and doesn't have enough features, but the idea is to allow for separated distributions to declare their own Bazar App Manifests, if necessary, such that root users can install micro backend services into the server 100% "visually".

Tightening security

This release allows you to manually provide a JWT token during setup. By default it will use some CSRNG gibberish, but you can manually override it, and provide manual seeds. This is important first of all to more easily allow for updating your Magic installation without throwing out existing users due to JWT parsing failures - However, more important, the JWT/auth secret is also used to seed the CSRNG Magic is using, or rather to add to its existing seed, both during setup and during restarts. This increases entropy in the internal CSRNG algorithm Magic is using as it is generating cryptography key pairs, session keys for crypto operations, etc - And hence is actually a significant tightening of the internal cryptographic operations within Magic's core, providing far better entropy for all cryptographic operations.

In addition the frontend is now built through its Docker images much more optimised, having turned on AOT, and other settings, that should result in smaller size, and faster execution speeds, etc.

Other changes includes more easily allowing for setting SMTP settings during pipeline builds, due to placeholders in the default "appsettings.json" file. Trapping JSON parsing exceptions in the "Endpoints" menu item if you invoke a payload endpoint, and you've got an error in your JSON syntax. Etc, etc, etc.

Windows authentication done

This release features among other things an extremely simple configuration path for configuring Windows authentication, in addition to allowing for easily use "external authentication grants", where Magic is no longer responsible for authenticating the user, but you can use alternative methods to accomplish this.

In addition the release also contains a whole range of minor bug fixes and UX improvements.

Bug fixes and UX/UI improvements

Besides from half a dozen minor bug fixes, this release features some UX and UI improvements. First of all, the main routing URL now contains a "dashboard" type of component, with large icons, leading to each individual module, explaining rapidly what the different modules do. In addition there are some minor improvements in Hyper IDE, such as tracking whether or not files are dirty, warning user as he tries to close these that they're unsaved. This release also features some minor bug fixes in the "Sockets" menu item, "Crypto" menu item, etc.

Better UX in dashboard + severe Angular error fixed

Unfortunately I had a bogus .gitignore file in the last release, that would ignore crucial components in the frontend. Sorry about that, this is now fixed.

Also there's a much nicer dashboard landing page now, giving you better links to each individual component, with some text describing roughly what the component does.

Better UI for sockets dashboard

This release features improvements in the dashboard parts, specifically how to manage socket connections, and subscribe to and publish messages.

Minor bugfix

Sometimes when going to "Diagnostics/Sockets" and creating a subscription, the existing connections doesn't correctly update, because the server has still not yet created the connection for some reasons. I am not sure why this happens, but I assume there is something in SignalR not having completely created the connection quite yet as we create the connection in our Magic code.

To accommodate for this, I have added a wait 500 millisecond parts after creating a subscription in the dashboard before I retrieve the existing connections again from the backend, since otherwise it becomes impossible to actually send messages to the connection unfortunately.

Sorry about that ...

More dashboard tools for web sockets and SignalR

This releases primarily features a lot of new dashboard tools to allow you to play around with web sockets, such as the ability to from within the "Diagnostics/Sockets" menu item create SignalR subscriptions, and see messages published by the server. This allows you to play around with your own socket applications created in Magic, to verify correct functionality, and see the flow of messages.

Active Directory or Windows authentication support

This release provides optional support for authenticating your users over your Windows Active Directory using SSO (Single Sign On), having users provide their Windows credentials. To use this feature, check out the magic.lambda.ad-auth project.

It basically works by allowing you to include one NuGet package, for then to exchange the default password invocation to an invocation that checks your AD credentials through a simple configuration setting. This again exchanges the default password invocation with checking your Windows credentials instead in your Windows AD.

The logic is completely interchangeable, allowing you to also provide your own external authentication scheme, completely independently, dynamically exchanging which slot to invoke to check your users' passwords.