Merge pull request #675 from DuendeSoftware/update-overview-pngs-to-svg

Switch images from PNG to SVG versions

Author: khalidabuhakmeh

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/images/application-architecture.svg

@@ -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/overview/images/middleware.svg

@@ -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/overview/images/protocols.svg

@@ -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.