Switch images from PNG to SVG versions

src/content/docs/identityserver/fundamentals/users.md

@@ -48,7 +48,7 @@ It is very important that you understand how it works when building the login pa
 Recall the diagram showing the relationship of your custom UI pages and the IdentityServer middleware in your
 IdentityServer host application:
 
-![middleware diagram](../overview/images/middleware.png)
+![middleware diagram](../overview/images/middleware.svg)
 
 When your IdentityServer receives an authorize request, it will inspect it for a current authentication session for a
 user. This authentication session is based on ASP.NET Core's authentication system and is ultimately determined by a
@@ -58,7 +58,7 @@ If the user has never logged in there will be no cookie, and then the request to
 redirect to your login page. This is the entry point into your custom workflow that can take over to get the user logged
 in.
 
-![sign in flow](../ui/images/signin_flow.png)
+![sign in flow](../ui/images/signin_flow.svg)
 
 Once the login page has finished logging in the user with the ASP.NET Core authentication system, it will redirect the
 user back to the authorize endpoint.

src/content/docs/identityserver/overview/big-picture.md

@@ -12,7 +12,7 @@ redirect_from:
 
 Most modern applications look more or less like this:
 
-![an architecture diagram for modern applications with clients and services](./images/appArch.png)
+![an architecture diagram for modern applications with clients and services](./images/application-architecture.svg)
 
 The most common interactions are:
 
@@ -31,7 +31,7 @@ across those applications and endpoints.
 
 Restructuring the application to support a security token service leads to the following architecture and protocols:
 
-![an architecture diagram showing where OAuth 2.0 is used](./images/protocols.png)
+![an architecture diagram showing where OAuth 2.0 is used](./images/protocols.svg)
 
 Such a design divides security concerns into two parts:
 
@@ -78,7 +78,7 @@ depending on your needs)
 and add the IdentityServer middleware to that application. The middleware adds the necessary protocol heads to the
 application so that clients can talk to it using those standard protocols.
 
-![IdentityServer middleware diagram and its relatinship in the ASP.NET Core pipeline](./images/middleware.png)
+![IdentityServer middleware diagram and its relatinship in the ASP.NET Core pipeline](./images/middleware.svg)
 
 The hosting application can be as complex as you want, but we typically recommend to keep the attack surface as small as
 possible by including

src/content/docs/identityserver/overview/terminology.md

@@ -12,7 +12,7 @@ redirect_from:
 
 The specs, documentation and object model use a certain terminology that you should be aware of.
 
-![a basic diagrams showing the relationship between users, clients, identityserver, and resources](./images/terminology.png)
+![a basic diagrams showing the relationship between users, clients, identityserver, and resources](./images/terminology.svg)
 
 ## Duende IdentityServer
 

src/content/docs/identityserver/ui/ciba.md

@@ -30,7 +30,7 @@ A nice feature of this workflow is that the user does not enter their credential
 
 Below is a diagram that shows the high level steps involved with the CIBA workflow and the supporting services involved.
 
-![Showing how CIBA works in diagram form](./images/ciba.png)
+![Showing how CIBA works in diagram form](./images/ciba.svg)
 
 
 * **Step 1**: IdentityServer exposes a [backchannel authentication request endpoint](/identityserver/reference/endpoints/ciba) that the client uses to initiate the CIBA workflow.

src/content/docs/identityserver/ui/federation.md

@@ -15,7 +15,7 @@ Federation means that your IdentityServer offers authentication methods that use
 If you offer a number of these external authentication methods, often the term *Federation Gateway* is used to describe
 this architectural approach.
 
-![Diagram showing the benefits of using a federation gateway](./images/federation.png)
+![Diagram showing the benefits of using a federation gateway](./images/federation.svg)
 
 Generally, this architecture allows shielding your client applications from the complexities of your authentication
 workflows and business requirements that go along with them.

src/content/docs/identityserver/ui/index.md

@@ -21,7 +21,7 @@ The design goal of Duende IdentityServer is to provide a full implementation of
 
 To allow full flexibility of the UI, including business rules and user flow, the UI is separated from the core IdentityServer engine. The engine implements the endpoints specified in the protocols and hands off control to your code in the UI as necessary.
 
-![diagram showing how IdentityServer middleware is hosted in an ASP.NET Core application](./images/host.png)
+![diagram showing how IdentityServer middleware is hosted in an ASP.NET Core application](./images/host.svg)
 
 Our templates include a [quick start UI](/identityserver/quickstarts/2-interactive/#add-the-ui) and a [quick start UI adapted to ASP.NET Identity](/identityserver/quickstarts/5-aspnetid/) which provide a starting point for all the necessary pages, ready to be customized.
 

src/content/docs/identityserver/ui/server-side-sessions/inactivity-timeout.md

@@ -41,7 +41,7 @@ Internally IdentityServer provides a `ISessionCoordinationService` which is invo
 Its purpose is to then extend the lifetime of the server-side session. 
 Below is a picture of the various types of requests to do this:
 
-![diagram demonstrating how to extend a session using IdentityServer](./images/extending_session.png)
+![diagram demonstrating how to extend a session using IdentityServer](./images/extending_session.svg)
 
 
 ### User Inactivity Detection and Session Termination
@@ -54,7 +54,7 @@ Clients that receive back-channel logout would know the user's session has ended
 But if back-channel is not used, then the client would need some other signal to consider the user's session has ended.
 The obvious signal would be if the refresh token request failed, then that would be an appropriate signal that the user's session has also ended.
 
-![A diagram showing what happens when a session expires](./images/session_expired.png)
+![A diagram showing what happens when a session expires](./images/session_expired.svg)
 
 Given this understanding, client applications can participate in this convention and IdentityServer can coordinate to achieve this system-wide "inactivity timeout" requirement.