- {icon && 
}
+ {icon && }
'
```
-The response should look look similar to below, however it has been formatted here for readability:
+The response should look similar to below, however it has been formatted here for readability:
```json
{
@@ -340,7 +340,7 @@ curl --location 'http://localhost:9001/make-change?total=3.24' \
--header 'Authorization: Bearer '
```
-The response should look look similar to below, however it has been formatted here for readability:
+The response should look similar to below, however it has been formatted here for readability:
```json
{
diff --git a/astro/src/content/quickstarts/quickstart-javascript-remix-web.mdx b/astro/src/content/quickstarts/quickstart-javascript-remix-web.mdx
new file mode 100644
index 0000000000..795d6df769
--- /dev/null
+++ b/astro/src/content/quickstarts/quickstart-javascript-remix-web.mdx
@@ -0,0 +1,315 @@
+---
+title: Remix
+description: Quickstart integration of Javascript Remix web application with FusionAuth
+navcategory: getting-started
+prerequisites: Node.js version 18
+section: web
+technology: Remix
+language: Javascript
+icon: /img/icons/remix.svg
+faIcon: fa-node-js
+color: green
+cta: EmailListCTA
+---
+
+import Aside from '/src/components/Aside.astro';
+import LoginAfter from '../../diagrams/quickstarts/login-after.astro';
+import LoginBefore from '../../diagrams/quickstarts/login-before.astro';
+import RemoteCode from '/src/components/RemoteCode.astro';
+
+In this quickstart, you will build an application with Remix and integrate it with FusionAuth. The application is for [ChangeBank](https://www.youtube.com/watch?v=pkH-kD73QUM), a global leader in converting dollars into coins. It will have areas reserved for logged in users and public-facing sections.
+
+Find the Docker Compose file and source code for the complete application at https://github.com/FusionAuth/fusionauth-quickstart-javascript-remix-web.
+
+## Prerequisites
+
+For this Quickstart, you'll need:
+
+* [Node 18](https://nodejs.org/en/download) or later.
+* [Docker](https://www.docker.com), which is the quickest way to start FusionAuth. (There are [other ways](/docs/v1/tech/installation-guide/)).
+
+## General Architecture
+
+While this sample application doesn't have login functionality without FusionAuth, a more typical integration will replace an existing login system with FusionAuth.
+
+In that case, the system might look like this before FusionAuth is introduced.
+
+`, you can specify which user details you want to keep in the session. This example uses a single string containing the user's email, but you could define an object with more details or just a user Id.
+
+Note that the `User` must have a value. If the Authenticator returns nothing to store in the session, then a user will not stay logged in.
+
+In `authOptions`, you specify the FusionAuth URLs stored in the `.env` file, which match those created by Kickstart when you ran the Docker command to start FusionAuth.
+
+Finally, `authStrategy` returns the user's email, decoded from the JWT returned by FusionAuth.
+
+### Routes
+
+First replace the homepage of your app in `mysite/app/routes/_index.tsx` with the following code.
+
+();` provides whatever data the loader function returns for use in the HTML. It's used in the line `
+
diff --git a/site/landing/php-apis/result.html b/site/landing/php-apis/result.html
new file mode 100644
index 0000000000..0645e82774
--- /dev/null
+++ b/site/landing/php-apis/result.html
@@ -0,0 +1,32 @@
+---
+layout: developer-container
+title: PHP APIs Cookie App Login
+description: PHP APIs Cookie App Login
+sitemap:
+ exclude: 'yes'
+---
+
+
diff --git a/site/legal/data-processing-addendum-v1.4.pdf b/site/legal/data-processing-addendum-v1.4.pdf
new file mode 100644
index 0000000000..2aad8a2a31
Binary files /dev/null and b/site/legal/data-processing-addendum-v1.4.pdf differ
diff --git a/src/generate-release-notes-stub.sh b/src/generate-release-notes-stub.sh
index 086b9415a1..596e161883 100755
--- a/src/generate-release-notes-stub.sh
+++ b/src/generate-release-notes-stub.sh
@@ -5,9 +5,13 @@ if [[ $# < 1 ]]; then
exit 1
fi
-# If we can get good at tagging things correctly "bug", "enhancement", "feature" we should be able to make this produce the stub
-# for each section in the release notes - or get close.
+# Issues should be labeled with exactly one of: "bug", "enhancement", "feature", "security", or "internals"
+# Without one of these labels, they won't be included
+# If an issue has multiple labels, it will be repeated
#
+# An Issue's body should end with a '### Release Notes' section and list items to be included
+# Otherwise, they default to the issue title
+
milestone=$1
date=$(date +"%B %-d, %Y" | sed 's/1,/1st,/;s/2,/2nd,/;s/3,/3rd,/;s/\([0-9]\),/\1th,/')
@@ -16,22 +20,35 @@ echo ""
echo "== Version ${milestone}"
echo "_${date}_"
echo ""
+echo "include::docs/v1/tech/__database-migration-warning.adoc[]"
+echo ""
echo "=== Known Issues"
-echo "=== Security"
-echo "=== Changed"
-echo "=== Fixed"
-echo "=== Enhancements"
-echo "=== New"
-echo "=== Internal"
echo ""
+gh_issue_list() {
+ label=$1
+ header=$2
+ echo "=== $header"
+ set -o noglob # don't be globbing files in my backticks
-gh issue list --repo FusionAuth/fusionauth-issues -m $milestone -L 250 --search "sort:created-asc" --json number,body,title --jq ".[]|[.number,.body,.title] | @tsv" |
-while IFS=$'\t' read -r number body title; do
- generated_title=`echo $body | awk -F'--release-notes--' '{print $2, $3}'`
- if [[ "${generated_title}" == " " ]]; then
- generated_title=${title}
- fi
- echo "* $generated_title"
- echo "** Resolves https://github.com/FusionAuth/fusionauth-issues/issues/$number[GitHub Issue #$number]"
-done
+ gh issue list --repo FusionAuth/fusionauth-issues -m $milestone -L 250 --label $label --search "sort:created-asc" --json number,body,title --jq ".[]|[.number,.body,.title] | @tsv" |
+ while IFS=$'\t' read -r number body title; do
+ generated_copy=`echo $body | awk -F'### Release Notes' '{print $2}'`
+ if [[ "${generated_copy}" == "" ]]; then
+ generated_copy=${title}
+ else
+ generated_copy=`echo $generated_copy | sed 's#\\\\r\\\\n#\n#g'`
+ fi
+ echo "* ${generated_copy#[$'\r\t\n ']}"
+ echo "** Resolves https://github.com/FusionAuth/fusionauth-issues/issues/$number[GitHub Issue #$number]"
+ done
+ echo ""
+}
+gh_issue_list "changed" "Changed"
+gh_issue_list "feature" "New"
+gh_issue_list "security" "Security"
+gh_issue_list "bug" "Fixed"
+gh_issue_list "enhancement" "Enhancements"
+gh_issue_list "internals" "Internal"
+
+echo ""
-
+
diff --git a/astro/src/content/articles/oauth/value-standards-compliant-authentication.md b/astro/src/content/articles/oauth/value-standards-compliant-authentication.md
index 81bbe2ffcf..aaa15f15ea 100644
--- a/astro/src/content/articles/oauth/value-standards-compliant-authentication.md
+++ b/astro/src/content/articles/oauth/value-standards-compliant-authentication.md
@@ -6,7 +6,7 @@ image: advice/value-standards/the-value-of-standards-compliant-authentication-he
section: OAuth
date: 2021-06-10
dateModified: 2021-06-10
-icon: /img/icons/complete-list-oauth-2-grants.svg
+icon: /img/icons/value-standards-authentication.svg
---
Software applications regularly need access to data from other services on behalf of their users.
diff --git a/astro/src/content/blog/dotnet-templates.mdx b/astro/src/content/blog/dotnet-templates.mdx
new file mode 100644
index 0000000000..ae456f0ca6
--- /dev/null
+++ b/astro/src/content/blog/dotnet-templates.mdx
@@ -0,0 +1,226 @@
+---
+publish_date: 2023-10-26
+title: Create .NET web applications with FusionAuth templates
+description: Reduce the overhead associated with customer authentication and authorization when creating a .NET web application using FusionAuth templates.
+authors: Mark Robustelli
+image: /img/blogs/dotnet-templates/header-fusionauth-dotnet-templates.png
+categories: Product, Education, Engineering
+tags: dotnet template mvc blazor webapi
+excerpt_separator: "{/* more */}"
+---
+import RemoteCode from '../../components/RemoteCode.astro';
+import Aside from '/src/components/Aside.astro';
+
+Reduce the overhead associated with customer authentication and authorization when creating a .NET web application using FusionAuth templates.
+{/* more */}
+
+## Introduction
+*Templates for nothin' and your security for free.*
+
+Literally. The [FusionAuth Templates for Microsoft .NET](https://marketplace.visualstudio.com/items?itemName=FusionAuth.FusionAuthVSTemplates) are free to use and so is the self-hosted [Community Plan](/pricing?step=plan&hosting=self-hosting) of FusionAuth.
+
+As a Developer Relations Engineer at FusionAuth, my goal is to help developers develop faster. That's why I'm so excited about the release of our new .NET templates. They're available through the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=FusionAuth.FusionAuthVSTemplates) and as a [NuGet](https://www.nuget.org/packages/FusionAuth.Templates) package, making it easy for developers to get started with FusionAuth and build secure applications quickly and easily.
+
+## Getting Started
+
+### Download The Templates
+
+Let's start by installing the FusionAuth templates using Visual Studio. For those who develop .NET applications outside of Visual Studio, don't worry I'll cover that too. Inside Visual Studio, select `Extensions` from the menu bar and then select `Manage Extensions`.
+
+
+Enter `FusionAuth` in the search bar. Then, select `Download` when you find the templates. You will need to restart Visual Studio after the templates are downloaded and installed.
+
+
+For those of you who develop outside of Visual Studio, you can simply issue the following command from the terminal or command line.
+
+```shell
+dotnet new install FusionAuth.Templates::1.0.0
+```
+
+That's all there is to obtaining the templates.
+
+### FusionAuth Server
+
+Of course, to effectively use these templates you will need an instance of FusionAuth to bang against. If you already have an instance set up, you likely know the settings you will need. If you do not have an instance to point to, don't fear. You can download an instance and have it up and running in no time assuming you have Docker installed. Simply clone the [fusionauth-example-client-libraries](https://github.com/FusionAuth/fusionauth-example-client-libraries) info, and spin up the Docker instance using the following command.
+
+```shell
+mkdir fusionauth-templates-example
+cd fusionauth-templates-example
+git clone https://github.com/FusionAuth/fusionauth-example-client-libraries.git
+cd fusionauth-example-client-libraries
+docker compose up -d
+```
+
+If things go according to plan, you should now have a fully functioning instance of FusionAuth that has been pre-configured to work with the templates. That means that an application with users has been set up in FusionAuth and you are ready to start developing your application.
+
+If things do not go according to plan, you can find more details in the [Readme.md](https://github.com/FusionAuth/fusionauth-example-client-libraries/blob/main/README.md) file in the repository. You could also check out one of our quickstarts, such as [.NET Web](/docs/quickstarts/quickstart-dotnet-web) for more details on how to get the FusionAuth server up and running.
+
+## Setup the Project
+
+If Visual Studio is not your thing, don't fret. I'll have something for you in a bit. For now, you will head back to Visual Studio. Open it up and select `New Project`.
+
+
+
+You should now see the FusionAuth templates as an option to start your project. If you do not see them listed, simply search for `FusionAuth` in the `Search for templates` search bar.
+
+
+
+For this blog, we will select the `FusionAuth ASP.NET MVC Web App`. You will be prompted to enter the name of your project. Once you do that and select `Next`, you will be presented with a window that will allow you to enter the information for your FusionAuth server. If you set up the server using the docker image described above, you will not need to change anything except the `FusionAuth Application Client Secret`. You can update the input with the correct secret by entering `change-this-in-production-to-be-a-real-secret`. If you have another FusionAuth server, you will need to update the inputs with the appropriate information.
+
+
+
+If you are not using Visual Studio and you installed the templates using the NuGet package, you can issue the following command from the Command Prompt in Windows (or Terminal window on a Mac) in an empty directory and it will create the project for you.
+
+```shell
+mkdir fusionauth-template-example
+cd fusionauth-template-example
+dotnet new fusionauthmvcwebapp --client-secret "change-this-in-production-to-be-a-real-secret" --name "MyFusionAuthTestApplication"
+```
+
+## It Is Just That Simple
+
+It is just that simple. You now have a fully functioning and secured application. All you need to do is hit the green Start button in Visual Studio.
+
+Again, if you are not using Visual Studio all you need to do is issue the following command from the same directory the `.csproj` file is in.
+
+```shell
+cd MyFusionAuthTestApplication
+dotnet run
+```
+
+You can open a browser and go to [https://localhost:5001](https://localhost:5001). Log in using the username `admin@example.com` and the password `password`.
+
+## Alright, Show Me The Code Already
+
+Okay, for some, you have seen all you need to see to start using the new Visual Studio FusionAuth .NET Templates. Please enjoy and feel free to head to the Conclusion section.
+
+For those of you who like to peek under the hood, I have reserved this section for you. Let's dig in.
+
+First things first. Let's take a look at where the values are stored from the inputs you were prompted for when creating the project. Take a look at the `appsettings.json`. There you will find the `Issuer` and `ClientId` that you entered.
+
+```json
+"FusionAuth": {
+ "Issuer": "http://localhost:9011",
+ "ClientId": "e9fdb985-9173-4e01-9d73-ac2d60d1dc8e"
+}
+```
+
+ In the `appsettings.Development.json`, you will find the `ClientSecret` and the Kestrel `Url` that will determine which port the application will run on in development.
+
+```json
+"FusionAuth": {
+ "ClientSecret": "change-this-in-production-to-be-a-real-secret"
+},
+"Kestrel": {
+ "Endpoints": {
+ "Https": {
+ "Url": "https://localhost:5001"
+ }
+ }
+}
+```
+
+
+
+It is also important to know that a reference to the `Microsoft.AspNetCore.Authentication.OpenIdConnect` NuGet package has been added to the project.
+
+From here, it is a fairly standard implementation of a MVC application.
+
+There is a shared layout view `Views\Shared\_Layout.cshtml` which will give you a menu bar across the top and then the body of the page below.
+
+
+
+This is also where the logic to display the `Login` link or the `Profile` and `Logout` links in the menu bar is stored.
+
+```html
+
+ ```
+
+If the user is not logged in and clicks the `Login` link, they will be taken to the `AccountController` triggering the `Login` function. This function will take the values in the settings and issue the login dialog for the user.
+
+```c#
+public async Task Login(string returnUrl = "/")
+ {
+ var authenticationProperties = new AuthenticationProperties();
+ authenticationProperties.RedirectUri = returnUrl;
+
+ await HttpContext.ChallengeAsync("FusionAuth", authenticationProperties);
+ }
+```
+After the user is authenticated, it redirects them to the homepage again. This time they will be authenticated and will be presented with the `Profile` and `Logout` links.
+
+The `Logout` link will again take the user to the `AccountController` and perform the logout logic.
+
+```c#
+public async Task Logout()
+{
+ var authenticationProperties = new AuthenticationProperties();
+ authenticationProperties.RedirectUri = Url.Action("Index", "Home");
+
+ await HttpContext.SignOutAsync("FusionAuth", authenticationProperties);
+ await HttpContext.SignOutAsync(CookieAuthenticationDefaults.AuthenticationScheme);
+}
+```
+
+The `Profile` link will take to user to the `AccountController` and attempt to return the `Profile` view. Notice the `Authorize` attribute above the function name. This attribute lets the application know not to issue this view unless the user is authenticated.
+
+```c#
+[Authorize]
+public IActionResult Profile()
+{
+ return View(User);
+}
+```
+
+For this template, the `Profile` simply returns some claims. However, in your application, this is where your secured application would start.
+
+
+
+## Conclusion
+Authentication and Authorization are a critical part of any application. You could create that all from scratch, but it often does not make sense to do so. When you decide to use FusionAuth, you could also create that integration from scratch as demonstrated in many of [FusionAuth's Quickstarts](/docs/quickstarts/). However, you don't need to. The point of the templates is to reduce the amount of time and overhead spent plumbing the application so you can concentrate on creating the parts of it that separate you from your competition. I hope the next time you sit down to write your latest and greatest .NET application you choose to utilize the power of the FusionAuth .NET Templates.
+
+## Next steps
+
+If you enjoyed this article, I suggest you download the FusionAuth .NET Templates and create your project with them. Please check out some of the other links and resources about FusionAuth and the .NET Templates.
+
+* [Download FusionAuth for Free](/download)
+* [FusionAuth .NET Templates in Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=FusionAuth.FusionAuthVSTemplates)
+* [FusionAuth .NET Templates in NuGet](https://www.nuget.org/packages/FusionAuth.Templates)
+* [FusionAuth - Getting Started](/docs/v1/tech/getting-started/)
+
diff --git a/astro/src/content/blog/fusionauth-longhornphp-2023.mdx b/astro/src/content/blog/fusionauth-longhornphp-2023.mdx
new file mode 100644
index 0000000000..703e6cafcc
--- /dev/null
+++ b/astro/src/content/blog/fusionauth-longhornphp-2023.mdx
@@ -0,0 +1,44 @@
+---
+publish_date: 2023-10-25
+title: "We'll see you at Longhorn PHP 2023"
+description: FusionAuth will be at Longhorn PHP. Say hi!
+authors: Dan Moore
+image: /img/blogs/longhorn-php-2023/longhorn-php-2023-event.png
+categories: Events
+tags: events, longhornphp, conference
+excerpt_separator: "{/* more */}"
+---
+
+Longhorn PHP is a long running community driven PHP conference taking place in Austin, Texas next week. I will be presenting and would love to see you there.
+
+{/* more */}
+
+## Why I am attending
+
+I was selected to give two different sessions, [one on JWTs](https://www.longhornphp.com/sessions#what-php-developers-need-to-know-about-jwts) and a [workshop on protecting your APIs](https://www.longhornphp.com/sessions#protecting-your-apis). I'm especially excited about the hands-on workshop, where users will, using a [web based training platform](https://instruqt.com/), explore various options of protecting an API written in PHP.
+
+For this workshop, we'll start with an unprotected Chuck Norris joke API. (A sample joke: "Chuck Norris makes onions cry."). Participants will then protect the API with a variety of methods, ending up with an API protected with an OAuth2 access token issued by an authorization server.
+
+I also look forward to connecting with the PHP community. I've worked in PHP off and on for decades. I wrote a raw PHP app in the early 2000s for a book club. I supported a local food directory in CakePHP for over a decade. And I've worked professionally with PHP solutions like Wordpress and Drupal.
+
+But I'm less familiar with more modern PHP frameworks and solutions like Laravel. When I've glanced at them, I've thought "that looks a lot like Rails" and my heart warms. So this is a great chance for me to learn more about what PHP folks are working on nowadays
+
+In particular, I'm looking forward to [Serializing Modern PHP](https://www.longhornphp.com/sessions#serializing-modern-php) and [Minimal vs. functional: “Clean” code as a practical – rather than aesthetic – virtue](https://www.longhornphp.com/sessions#minimal-vs-functional-clean-code-as-a-practical---rather-than-aesthetic---virtue), but there are of course a number of great sessions.
+
+## Community conferences
+
+It's great to be able to give talks about topics I'm interested in, but I'm also attending because community driven conferences are fantastic. We need more of them.
+
+* They're entry points for attendees into the wider developer community, especially newer developers
+* There are fewer developers than at bigger conferences, but the attendees are more engaged
+* You can interact with developers and users in a far more personal and high-bandwidth fashion
+* They're an important step on the ladder for newer speakers; more professional than a meetup, less intimidating than a large conference like Re:Invent or KubeCon
+
+We lost a lot of these events during the last few years. Community conferences are difficult to run, and require buckets of volunteer time and money. In my experience, no one does a community conference for the money.
+
+I'm glad I can attend Longhorn PHP and hope you can too. There are still [tickets available](https://ti.to/longhorn-php/longhorn-php-2023), including a virtual only option.
+
+## Meet up
+
+If you want to meet up with me at Longhorn PHP, I'll be around! Ping me on [LinkedIn](https://www.linkedin.com/in/mooreds/) or [Twitter/X](https://twitter.com/mooreds), or [fill out our contact form](/contact) and I'll see it.
+
diff --git a/astro/src/content/quickstarts/quickstart-golang-api.mdx b/astro/src/content/quickstarts/quickstart-golang-api.mdx
index 13b04b910c..229171ba5f 100644
--- a/astro/src/content/quickstarts/quickstart-golang-api.mdx
+++ b/astro/src/content/quickstarts/quickstart-golang-api.mdx
@@ -94,7 +94,7 @@ go run main.go
You can then follow the instructions in the Run the API section started at Get a Token.
-To create the application from scratch, make a directory for this API.
+To create the application from scratch, make a directory for this API.
```
mkdir your-application && cd your-application
@@ -194,7 +194,7 @@ There is a lot of code in this function. Let's break it down:
Now, you will add the code to set the public key. This function will accept the key Id from the token and call the authorization server to get the public key with that key Id and put it in the proper format to be used.
+
{ comingSoon ? title + ' * Coming Soon' : title }
{email}
`. + +The final page you need is `mysite/app/routes/change.tsx`, with the following code. + +
+
+
+
+
+
+ + Login with walker@example.com or trivette@example.com +
++ Log In +
+
+
+
+
+
+
+ + Thanks for logging in. Here are the cookies that JavaScript on this page can see. +
++ +
+