v1.1.1 release (#16)

Co-authored-by: CDR Open Source <opensource@cdr.gov.au>

Author: CDR-FarooqK

.azuredevops/pipelines/build-v2.yml

@@ -386,7 +386,7 @@ jobs:
         displayName: "Install dotnet-ef"
         condition: always()
         inputs:
-          script: "dotnet tool install --global dotnet-ef"
+          script: "dotnet tool install --version 7.0.13 --global dotnet-ef"
 
       - task: CmdLine@2
         displayName: "Check dotnet-ef version"

.github/workflows/codeql-analysis.yml

@@ -67,21 +67,9 @@ jobs:
         # Prefix the list here with "+" to use these queries and those in the config file.
         # queries: ./path/to/local/query, your-org/your-repo/queries@main
 
-    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
-    # If this step fails, then you should remove it and run the build manually (see below)
-    - name: Autobuild
-      uses: github/codeql-action/autobuild@v2
-
-    # ℹ️ Command-line programs to run using the OS shell.
-    # 📚 https://git.io/JvXDl
-
-    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
-    #    and modify them (or add more) to build your code if your project
-    #    uses a compiled language
-
-    #- run: |
-    #   make bootstrap
-    #   make release
+    - name: Build solution
+      run: |
+        dotnet build ./Source/CdrAuthServer.sln --configuration 'Release'
 
     - name: Perform CodeQL Analysis
       uses: github/codeql-action/analyze@v2

.github/workflows/docker.yml

@@ -78,3 +78,12 @@ jobs:
 
     - name: Image digest
       run: echo ${{ steps.docker_build.outputs.digest }}
+
+    - name: Docker Hub Description
+      if: ${{ github.repository_owner == 'ConsumerDataRight' && github.ref_name == 'main' }}
+      uses: peter-evans/dockerhub-description@v3
+      with:
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
+        repository: ${{ env.DOCKER_IMAGE }}
+        enable-url-completion: true

.github/workflows/sonarcloud-analysis.yml

@@ -31,25 +31,26 @@ jobs:
     runs-on: windows-latest
 
     steps:
-      - name: Set up JDK 11
-        uses: actions/setup-java@v1
+      - name: Set up JDK 17
+        uses: actions/setup-java@v3
         if: ${{ env.sonarSecret != 0 }} # Only run scan if secret use is allowed - requires secrets to run successfully
         with:
-          java-version: 1.11
-      - uses: actions/checkout@v2
+          java-version: 17
+          distribution: 'zulu' # Alternative distribution options are available.
+      - uses: actions/checkout@v3
         if: ${{ env.sonarSecret != 0 }} # Only run scan if secret use is allowed - requires secrets to run successfully
         with:
           fetch-depth: 0  # Shallow clones should be disabled for a better relevancy of analysis
       - name: Cache SonarCloud packages
-        uses: actions/cache@v2.1.6
+        uses: actions/cache@v3
         if: ${{ env.sonarSecret != 0 }} # Only run scan if secret use is allowed - requires secrets to run successfully
         with:
           path: ~\sonar\cache
           key: ${{ runner.os }}-sonar
           restore-keys: ${{ runner.os }}-sonar
       - name: Cache SonarCloud scanner
         id: cache-sonar-scanner
-        uses: actions/cache@v2.1.6
+        uses: actions/cache@v3
         if: ${{ env.sonarSecret != 0 }} # Only run scan if secret use is allowed - requires secrets to run successfully
         with:
           path: .\.sonar\scanner

CHANGELOG.md

@@ -1,16 +1,27 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
-## [1.0.3] - 2023-10-26
+## [1.1.1] - 2023-11-29
 
 ### Changed
 - Updated npm packages used for Authorisation Server User Interface.
 
+## [1.1.0] - 2023-10-26
+
+### Changed
+- Updated npm packages used for Authorisation Server User Interface.
+- Refactored automated tests to use a shared NuGet package.
+
+## [1.0.3] - 2023-10-03
+
+### Changed
+- Configurable OSCP check added for mtls client certificates. By default it is disabled.
+
 ## [1.0.2] - 2023-06-20
 
 ### Changed

CODE_OF_CONDUCT.md

@@ -115,8 +115,8 @@ the community.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
 Community Impact Guidelines were inspired by 
 [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
@@ -126,7 +126,7 @@ For answers to common questions about this code of conduct, see the FAQ at
 at [https://www.contributor-covenant.org/translations][translations].
 
 [homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations

Help/debugging/HELP.md

@@ -1,55 +1,57 @@
-<h2>To get started, clone the source code</h2>
-<div style="margin-left:18px;">
-1. Create a folder called CDR<br />
-2. Navigate to this folder<br />
-3. Clone the repo as a subfolder of this folder using the following command;<br />
-<div style="margin-left:18px;">
-git clone https://github.com/ConsumerDataRight/authorisation-server.git<br />
-</div>
-4. Install the required certificates. See certificate details <a href="../../CertificateManagement/README.md" title="Certificate Management" alt="Certificate Management - CertificateManagement/README.md"> here</a>.<br />
-5. Start the projects in the solution, can be done in multiple ways, examples below are from .Net command line and using MS Visual Studio<br />
-</div>
-
-<h2>.Net command line</h2>
-<div style="margin-left:18px;">
-<p>1. Download and install the free <a href="https://docs.microsoft.com/en-us/windows/terminal/get-started" title="Download the free Windows Terminal here" alt="Download the free MS Windows Terminal here">MS Windows Terminal</a>
-<br />
-2. Use the <a href="../../Source/Start-Auth-Server.bat" title="Use the Start-Auth-Server .Net CLI batch file here" alt="Use the Start-Auth-Server .Net CLI batch file here">Start-Auth-Server</a> batch file to build and run the required projects to start the Mock Data Holder.
-</p>
+# Getting Started
+To get started, clone the source code from the GitHub repositories by following the steps below:
+
+1. Create a folder called CDR.
+2. Navigate to this folder.
+3. Clone the repo as a subfolder of this folder using the following command:
+```
+git clone https://github.com/ConsumerDataRight/authorisation-server.git
+```
+4. Install the required certificates. See certificate details [here](../../CertificateManagement/README.md "Certificate Management").  
+5. Start the projects in the solution. This can be done in multiple ways. This guide explains how to do this using .Net command line and using MS Visual Studio.
+
+## .Net command line
+
+1. Download and install the free [MS Windows Terminal](https://docs.microsoft.com/en-us/windows/terminal/get-started "Download the free Windows Terminal here").
+2. Use the [Start-Auth-Server](../../Source/Start-Auth-Server.bat "Use the Start-Auth-Server.bat .Net CLI batch file here") batch file to build and run the required projects to start the Mock Data Holder.
+
 
 [<img src="./images/DotNet-CLI-Running.png"  width='600' alt="Start projects from .Net CLI"/>](./images/DotNet-CLI-Running.png)
-<br />
-This will create the LocalDB database by default and seed the database with the supplied sample data.
-<p>LocalDB is installed as part of MS Visual Studio. If using MS VSCode, the MS SQL extension will need to be installed.</p>
-<p>You can connect to the database from MS Visual Studio using the SQL Explorer, or from MS SQL Server Management Studio (SSMS) using
-	the following settings; <br />
-	Server type: Database Engine <br />
-	Server name: (LocalDB)\MSSQLLocalDB <br />
-	Authentication: Windows Authentication<br />
-</p>
-</div>
-
-<h2>MS Visual Studio</h2>
-<div style="margin-left:18px;">
-<p>To launch the application using MS Visual Studio, the following projects need to be started:</p>
-<p>	CdrAuthServer <br />
-	CdrAuthServer.mTLS.Gateway <br />
-	CdrAuthServer.TLS.Gateway<br />
-</p>
-
-<p>1. Navigate to the solution properties and select a "Start" action for the required projects.</p>
+
+This will create the LocalDB instance by default and seed the database with the supplied sample data.
+
+LocalDB is installed as part of MS Visual Studio. If using MS VSCode, the MS SQL extension will need to be installed.
+
+You can connect to the database from MS Visual Studio using the SQL Explorer, or from MS SQL Server Management Studio (SSMS) using the following settings:
+```
+Server type: Database Engine  
+Server name: (LocalDB)\\MSSQLLocalDB  
+Authentication: Windows Authentication  
+```
+## MS Visual Studio
+
+### Start the Mock Data Holder
+To launch the application using MS Visual Studio, the following projects need to be started:
+```
+CdrAuthServer 
+CdrAuthServer.mTLS.Gateway
+CdrAuthServer.TLS.Gateway
+```
+	
+1. Navigate to the solution properties and select a "Start" action for the required projects.
 
 [<img src="./images/MS-Visual-Studio-Select-projects.png" width='600' alt="Project selected to be started"/>](./images/MS-Visual-Studio-Select-projects.png)
-<br />
-<p>2. Click "Start" to start the Authorisation Server solution.</p>
+
+2. Click "Start" to start the Authorisation Server solution.
 
 [<img src="./images/MS-Visual-Studio-Start-No-Debug.png" width='600' alt="Start the project"/>](./images/MS-Visual-Studio-Start-No-Debug.png)
-<br />
-Output windows will be launched for each of the projects set to start.   <br />
-These will show the logging messages as sent to the console in each of the running projects. E.g.<br />
+
+3. Output windows will be launched for each of the projects set to start. \
+   These will show the logging messages as sent to the console in each of the running projects. E.g.
+
 [<img src="./images/MS-Visual-Studio-Running.png" width='600' alt="Project running"/>](./images/MS-Visual-Studio-Running.png)
-<br />
-To run the solution in debug mode, simply follow the steps outlined above and click on the "Start" button as shown in the image below: <br />
-[<img src="./images/MS-Visual-Studio-Start.png" width='600' alt="Start the project"/>](./images/MS-Visual-Studio-Start.png)
 
-</div>
+4. To run the solution in debug mode, simply follow the steps outlined above and click on the "Start" \
+   button as shown in the image below: 
+
+[<img src="./images/MS-Visual-Studio-Start.png" width='600' alt="Start the project"/>](./images/MS-Visual-Studio-Start.png)