You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/customize-integrations/configure-data-model/setup-blueprint/properties/embedded-url/authentication.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,8 @@ The following diagram outlines the login scheme used to authenticate with your S
11
11
12
12
Here is an explanation of the login flow:
13
13
14
-
1. The widget will generate a PKCE `code_verifier` & `code_challange`;
15
-
2. The widget URL is set to the `authorizationUrl` along with the `clientId` and the generated `code_challange`;
14
+
1. The widget will generate a PKCE `code_verifier` & `code_challenge`;
15
+
2. The widget URL is set to the `authorizationUrl` along with the `clientId` and the generated `code_challenge`;
16
16
3. The widget will then be redirected to the SSO sign-in page;
17
17
4. The user will sign in using the SSO (If the user is already signed in to the SSO, this step will happen automatically);
18
18
5. The SSO sign-in page will redirect the widget back to https://app.getport.io with the authorization `code` as a URL hash parameter;
0 commit comments