2020.08.2 Prod RN publshed

okta · Aug 24, 2020 · aaf9c81 · aaf9c81
1 parent 6dc925d
commit aaf9c81
Show file tree

Hide file tree

Showing 408 changed files with 23,324 additions and 15,422 deletions.
diff --git a/en/prev/Content/Resources/Images/ImlicitAppPage_360x222.jpg b/en/prev/Content/Resources/Images/ImlicitAppPage_360x222.jpg
diff --git a/en/prev/Content/Resources/Images/Security/recent-activity-events.png b/en/prev/Content/Resources/Images/Security/recent-activity-events.png
diff --git a/en/prev/Content/Resources/Images/Security/recent-activity-signin.png b/en/prev/Content/Resources/Images/Security/recent-activity-signin.png
diff --git a/en/prev/Content/Resources/Images/access-gateway/edit-log-verbosity.png b/en/prev/Content/Resources/Images/access-gateway/edit-log-verbosity.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/OktaBHO_ManageAddOns.png b/en/prev/Content/Resources/Images/end-user-docs/OktaBHO_ManageAddOns.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/OktaToolbar_ManageAddOns.png b/en/prev/Content/Resources/Images/end-user-docs/OktaToolbar_ManageAddOns.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/RecentlyUsed.png b/en/prev/Content/Resources/Images/end-user-docs/RecentlyUsed.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/end_user_notifications_2.jpeg b/en/prev/Content/Resources/Images/end-user-docs/end_user_notifications_2.jpeg
diff --git a/en/prev/Content/Resources/Images/end-user-docs/new-eu-dashboard.png b/en/prev/Content/Resources/Images/end-user-docs/new-eu-dashboard.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/ov-enable-detailed-logging.png b/en/prev/Content/Resources/Images/end-user-docs/ov-enable-detailed-logging.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/ov-info-icon.png b/en/prev/Content/Resources/Images/end-user-docs/ov-info-icon.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/plugin-ie-activex-filter.png b/en/prev/Content/Resources/Images/end-user-docs/plugin-ie-activex-filter.png
diff --git a/en/prev/Content/Resources/Images/end-user-docs/plugin-password-disable-prompt.png b/en/prev/Content/Resources/Images/end-user-docs/plugin-password-disable-prompt.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/notification-factor-enroll.png b/en/prev/Content/Resources/Images/healthinsight/notification-factor-enroll.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/notification-factor-reset.png b/en/prev/Content/Resources/Images/healthinsight/notification-factor-reset.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/notification-password-changed.png b/en/prev/Content/Resources/Images/healthinsight/notification-password-changed.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/notification-signon.png b/en/prev/Content/Resources/Images/healthinsight/notification-signon.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/notification-suspicious.png b/en/prev/Content/Resources/Images/healthinsight/notification-suspicious.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/threatinsight-audit.png b/en/prev/Content/Resources/Images/healthinsight/threatinsight-audit.png
diff --git a/en/prev/Content/Resources/Images/healthinsight/threatinsight-block.png b/en/prev/Content/Resources/Images/healthinsight/threatinsight-block.png
diff --git a/en/prev/Content/Resources/Images/security-threatinsight-01_thumb_0_100.png b/en/prev/Content/Resources/Images/security-threatinsight-01_thumb_0_100.png
diff --git a/en/prev/Content/Resources/Images/security-threatinsight-01_thumb_0_150.png b/en/prev/Content/Resources/Images/security-threatinsight-01_thumb_0_150.png
diff --git a/en/prev/Content/Resources/Images/suspicious-activity-reporting-00_thumb_300_0.png b/en/prev/Content/Resources/Images/suspicious-activity-reporting-00_thumb_300_0.png
diff --git a/en/prev/Content/Resources/MasterPages/redirect.flmsp b/en/prev/Content/Resources/MasterPages/redirect.flmsp
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="utf-8"?>
+<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd">
+    <head>
+    </head>
+    <body> 
+    </body>
+</html>
diff --git a/en/prev/Content/Topics/Access-Gateway/about-application-policy.htm b/en/prev/Content/Topics/Access-Gateway/about-application-policy.htm
@@ -297,25 +297,25 @@
                                                 <div role="main" id="mc-main-content">
                                                     <h1>About application policy</h1>
                                                     <img src="../../Resources/Images/access-gateway/application-policy.01.png" alt="To add or modify policy first select the policy pane. " />
-                                                    <p>Use <span class="okta-feature-namesAccess Gateway">Access Gateway</span> to configure one or more access policies per application. Policies are applied to URI resources within an application and you can set them to achieve the following:</p>
+                                                    <p>Use <span class="okta-feature-namesAccess Gateway">Access Gateway</span> to configure one or more access policies per application. Policies are applied to URL resources within an application and you can set them to allow:</p>
                                                     <ul>
                                                         <li value="1">
-                                                            <p>Allow access to an application by any authenticated user (default).</p>
+                                                            <p>Access to an application by any authenticated user (default).</p>
                                                         </li>
                                                         <li value="2">
-                                                            <p>Allow no authentication access (to anyone) for an application.</p>
+                                                            <p>No authentication access (to anyone) for an application.</p>
                                                         </li>
                                                         <li value="3">
-                                                            <p>Allow specific user(s) access to an application.</p>
+                                                            <p>Specific users to access an application.</p>
                                                         </li>
                                                         <li value="4">
-                                                            <p>Allow specific group(s) access to an application.</p>
+                                                            <p>Specific groups to access an application.</p>
                                                         </li>
                                                         <li value="5">
-                                                            <p>Allow access to an application based on any IDP user profile attribute.</p>
+                                                            <p>Access to an application based on any IDP user profile attribute.</p>
                                                         </li>
                                                         <li value="6">
-                                                            <p>Allow granular access based on an application URI(s) or deep link(s).</p>
+                                                            <p>Granular access based on application URLs or deep links.</p>
                                                         </li>
                                                     </ul>
                                                 </div>

diff --git a/...ics/Access-Gateway/application-policy.htm → ...opics/Access-Gateway/about-log-levels.htm b/...ics/Access-Gateway/application-policy.htm → ...opics/Access-Gateway/about-log-levels.htm
diff --git a/en/prev/Content/Topics/Access-Gateway/about-oag-prereqs.htm b/en/prev/Content/Topics/Access-Gateway/about-oag-prereqs.htm
@@ -316,7 +316,7 @@ <h2><a name="UnderlyingHW"></a>Underlying hardware</h2>
                                                         <p>Okta <span class="okta-feature-namesAccess Gateway">Access Gateway</span> was built to use the SSE4.2 extensions to the x64 instruction set, which were made available with the Intel® Nehalem and AMD Bulldozer microarchitectures.  The server that runs <span class="okta-feature-namesAccess Gateway">Access Gateway</span> must, at a minimum, support that instruction set.</p>
                                                         <h2>Okta org</h2>
                                                         <p>The <span class="okta-feature-namesAccess Gateway">Access Gateway</span> configuration process requires a super admin account to configure your tenant as the identity provider. </p>
-                                                        <p>See <a href="configure-idp-okta.htm" class="MCXref xref">Configure your Okta tenant as Identity Provider</a>.</p>
+                                                        <p>See <a href="configure-idp-okta.htm" class="MCXref xref">Configure your Okta tenant as an Identity Provider</a>.</p>
                                                         <h2><a name="Firewall_Rules"></a>Firewall and access requirements</h2>
                                                         <h3>Ports and protocols</h3>
                                                         <p><span class="okta-feature-namesAccess Gateway">Access Gateway</span> requires various ports and protocols to be open for use.<br />The following table describes all required accesses.</p>

diff --git a/en/prev/Content/Topics/Access-Gateway/about-oag.htm b/en/prev/Content/Topics/Access-Gateway/about-oag.htm
@@ -323,17 +323,17 @@ <h1>About <span class="okta-feature-namesAccess Gateway">Access Gateway</span></
                                                             <p class="noteHeading">Note</p>
                                                             <p class="noteContent"><span class="okta-feature-namesAccess Gateway">Access Gateway</span> focuses on Web (HTTP/HTTPS) based applications and does not support other protocols.</p>
                                                         </div>
-                                                        <div>
-                                                            <p>The <span class="okta-feature-namesAccess Gateway">Access Gateway</span> deployment is typically composed of :</p>
-                                                            <ul>
-                                                                <li value="1">Okta tenant or Okta org (1):<br /> All implementations at Okta start with an Okta tenant. Your Okta tenant represents your real world application including users and applications and multifactor authentication. Users access their org and are presented with a list of administered application tiles, which can be used to access their applications. Your Okta tenant manages users, groups, profile information and other details. Your Okta tenant can be your Universal Directory or it can be linked to another universal directory. It can be a combination of the two as well. </li>
-                                                                <li value="2">Virtualization environment (2):<br /><span class="okta-feature-namesAccess Gateway">Access Gateway</span> is a virtual appliance and must be hosted in an appropriate virtualization environment. You can host <span class="okta-feature-namesAccess Gateway">Access Gateway</span> directly on any computer that supports Oracle Virtual Box v5.0 or later. You can also install it in other supported environments.  See <a href="support-matrix.htm">Okta Access Gateway Supported Technologies</a>.</li>
-                                                                <li value="3">Virtual appliance (3):<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> is a 100% self contained virtual appliance. You can download <span class="okta-feature-namesAccess Gateway">Access Gateway</span> from Okta org &gt; Settings &gt; Downloads and deploy it in a supported environment. After deployment, you can manage it using command line and GUI based tools. In high availability scenarios, you can deploy <span class="okta-feature-namesAccess Gateway">Access Gateway</span> as many times as needed to meet reliability and throughput requirements.</li>
-                                                                <li value="4">Protected applications (4):<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> protects application resources. These resources may be applications based on header, SAML, custom Web, Kerberos, or other web applications.</li>
-                                                                <li value="5">Policy:<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> can protect applications using fine grained application policy. You can define user groups and protect individual parts of applications by configuring relevant policy statements.</li>
-                                                            </ul>
-                                                            <img src="../../Resources/Images/access-gateway/access-gateway-components.png" id="img_new" alt="Access Gateway Component overview" />
-                                                        </div>
+                                                    </div>
+                                                    <div>
+                                                        <p>The <span class="okta-feature-namesAccess Gateway">Access Gateway</span> deployment is typically composed of :</p>
+                                                        <ul>
+                                                            <li value="1">Okta tenant or Okta org (1):<br /> All implementations at Okta start with an Okta tenant. Your Okta tenant represents your real world application including users and applications and multifactor authentication. Users access their org and are presented with a list of administered application tiles, which can be used to access their applications. Your Okta tenant manages users, groups, profile information and other details. Your Okta tenant can be your Universal Directory or it can be linked to another universal directory. It can be a combination of the two as well. </li>
+                                                            <li value="2">Virtualization environment (2):<br /><span class="okta-feature-namesAccess Gateway">Access Gateway</span> is a virtual appliance and must be hosted in an appropriate virtualization environment. You can host <span class="okta-feature-namesAccess Gateway">Access Gateway</span> directly on any computer that supports Oracle Virtual Box v5.0 or later. You can also install it in other supported environments.  See <a href="support-matrix.htm">Okta Access Gateway Supported Technologies</a>.</li>
+                                                            <li value="3">Virtual appliance (3):<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> is a 100% self contained virtual appliance. You can download <span class="okta-feature-namesAccess Gateway">Access Gateway</span> from Okta org &gt; Settings &gt; Downloads and deploy it in a supported environment. After deployment, you can manage it using command line and GUI based tools. In high availability scenarios, you can deploy <span class="okta-feature-namesAccess Gateway">Access Gateway</span> as many times as needed to meet reliability and throughput requirements.</li>
+                                                            <li value="4">Protected applications (4):<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> protects application resources. These resources may be applications based on header, SAML, custom Web, Kerberos, or other web applications.</li>
+                                                            <li value="5">Policy:<br /> <span class="okta-feature-namesAccess Gateway">Access Gateway</span> can protect applications using fine grained application policy. You can define user groups and protect individual parts of applications by configuring relevant policy statements.</li>
+                                                        </ul>
+                                                        <img src="../../Resources/Images/access-gateway/access-gateway-components.png" id="img_new" alt="Access Gateway Component overview" />
                                                     </div>
                                                 </div>
                                                 <!-- Back to Top button --><a href="#" class="sf-back-to-top"><span class="arrow"></span>Top</a>