Update of sso integration documentation

.gitignore

@@ -15,6 +15,7 @@ target
 *.tar
 *.asc
 *.tmp
+.vs
 *~
 .#*
 *#*#

changelog.d/4-docs/update-of-sso-integration-using-octa

@@ -0,0 +1 @@
+Documentation of setting up SSO integration with Okta was outdated with Okta Classic UI, the new version was updated using Oktas latest design.

docs/src/understand/single-sign-on/okta/main.md

@@ -12,32 +12,24 @@
 ### Okta setup
 
 - Log in into Okta web interface
-- Open the admin console and switch to the "Classic UI"
 - Navigate to "Applications"
-- Click "Add application"
+- Click "Create App Integration"
 
 ```{image} 001-applications-screen.png
 ```
 
 ______________________________________________________________________
 
-- Create a new application
+- Choose `SAML 2.0`
 
 ```{image} 002-add-application.png
 ```
 
 ______________________________________________________________________
 
-- Choose `Web`, `SAML 2.0`
-
-```{image} 003-add-application-1.png
-```
-
-______________________________________________________________________
-
 - Pick a name for the application in "Step 1" and continue
 
-```{image} 004-add-application-step1.png
+```{image} 003-add-application-step1.png
 ```
 
 ______________________________________________________________________
@@ -63,7 +55,7 @@ ______________________________________________________________________
 
 **(\*) Note**: The application username **must be** unique in your team, and should be immutable once assigned. If more than one user has the same value for the field that you select here, those two users will log in as a single user on Wire. And if the value were to change, users will be re-assigned to a new account at the next login. Usually, `email` is a safe choice but you should evaluate it for your case.
 
-```{image} 005-add-application-step2.png
+```{image} 004-add-application-step2.png
 ```
 
 ______________________________________________________________________
@@ -78,7 +70,7 @@ ______________________________________________________________________
 +-----------------------------------+------------------------------------------------------------------------+
 ```
 
-```{image} 006-add-application-step3.png
+```{image} 005-add-application-step3.png
 ```
 
 ______________________________________________________________________
@@ -87,11 +79,23 @@ ______________________________________________________________________
 - Find the "Identity Provider Metadata" link. Copy the link address (normally done by right-clicking on the link and selecting "Copy link location" or a similar item in the menu).
 - Store the link address somewhere for a future step.
 
-```{image} 007-application-sign-on.png
+```{image} 006-application-sign-on.png
 ```
 
 ______________________________________________________________________
 
+- In the case you are looking for Download of IdP Metadata and SAML Signing Certificates.
+- Under "Sign-On" tab, find (scroll down) SAML Signing Certificates section.
+- Click the Actions button next to the certificate.
+- Choosing View IdP metadata opens a new browser tab containing the metadata, you can then right-click the metadata and save it as a (.xml) file.
+- Choosing Download certificate will automatically save the certificate as a file.
+
+**(\*) Note**: To provide IdP metadata in Wire's Team Settings, file has to be saved as `.xml` file.
+
+```{image} 007-view-idp-metadata.png
+```
+______________________________________________________________________
+
 - Switch to the "Assignments" tab
 - Make sure that some users (or everyone) is assigned to the application. These are the users that will be allowed to log in to Wire using Single Sign On. Add the relevant users to the list with the "Assign" button.