1.6.0: Health and Redirects

Two major features:

1. A proper healthcheck endpoint at /_/health for some proper healthchecks.
2. When running behind a proxy the API and UI will automatically redirect requests to the hostname of your choice.

When you're running NetGoLynx behind a cluster of some sort it's very likely you'll be using both http://go/ and https://go.yourcompany.com as valid URLs for the server. It's also pretty likely that your GitHub or Okta login configuration will only work for https://go.yourcompany.com, even though users might attempt to log into the site at http://go/. In my experience this was a pretty good source of confusion.

The documentation now has information for configuring a known correct hostname so that users trying to hit the UI or API will be redirected to the URL of your choosing. This won't affect regular redirects, so http://go/wiki will still just immediately resolve to the wiki link, while http://go/ will redirect to https://go.yourcompany.com. You get performance and a better user experience at the same time!

Has your Security team grumbled about users using non-HTTPS links? Good news, you can avoid sending the raw http request at all by using the NetGoLynx Chrome Extension!

1.5.0: Add Info endpoint

Adds an endpoint at /_/Home/Info which just returns the service name and a version.

This ties into the (new!!!) NetGoLynx Browser Extension coming soon to Chrome and other browsers. This extension will automatically rewrite go/links to the full server URL. This can allow folks to use NetGoLynx in environments where they can't rely on the DNS search domain for their machines. For example, switching on and off a VPN, or if you can't configure DNS in the way you need.

1.4.0: True TLS Termination Transit Tech

New

A new section for the appsettings.json file allows for running the application behind a TLS-terminating load balancer. Previously this wasn't properly implemented and required workarounds that Chrome and other browsers stopped tolerating. You'll probably want to configure this appropriately for your environment now.

This makes it easier to run NetGoLynx in clusters, though a distributed cache for login support isn't ready quite yet. That should be coming shortly.

Other stuff

I've also added some documentation on spinning up a test instance locally.

The application is now on .NET 5! This should not have any externally visible effects.

v1.3.1 OAuth works in Chrome again

Chrome is actively enforcing the cookie SameSite=None requirement. It was about time I implemented it properly, so now OAuth workflows in Chrome should work properly again.

No other changes in this release, just the cookie fix.

V1.3.0 - Admins and SQLs

This release makes it a little easier to manage and maintain an existing GoLynx server. Ask me how I know it'd make it easier to manage and maintain an existing server...

Multiple Database Provider Support

#14

This release adds support for PostgreSQL and MS SQL Server as database backends for GoLynx. This was added specifically to allow for GoLynx to be deployed in a highly available configuration communicating to a common database backend. This is in addition to the existing SQLite backend which makes spinning up an instance nice and easy.

Admin account support

#4

Admin accounts are actually a thing now, though let's call management of them 'preview mode'. Accounts are added to an explicit list in the appsettings.json and will be identified as admins at login.

Admin accounts are able to view every list in the system, who owns it, and can delete them. As the API still doesn't support any kind of pagination it's possible to get a lot of results on this page. In theory the search system can handle this, as it'll display 500 results and let you use the search bar to quickly filter results.

Minor codebase improvements

• Extraneous forward slashes are dropped from the end of redirect resolution requests, to prevent go/link/ from failing to resolve as the proper go/link.
• The dockerfile uses the proper sdk image for building
• The default Okta API URLs remove the custom authentication server URL piece, to prevent errors if you aren't using that feature in Okta.

V1.2.0 - Okta Support

This release adds Okta OAuth support and brings the application up to aspnet core 3.0. Performance tests are still looking good even with the upgrade.

v1.1.0

Adds filtering to the list page for rapidly locating links. The filtering works on the shortcut, the target URL, as well as the description. This should make it easier to sort through large amounts of links quickly.