OKTA-976972 - Mobile iOS redirect guide updates (#5576)

* Add change to BrowserSignin from WebAuthenticationUI

* Updates to mobile redirect guide as per Akanksha Bhasin

* Updates from previous PR edit

Author: brianduffield-okta

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/index.md

@@ -13,7 +13,7 @@ Add authentication to your mobile app using the Okta [redirect model](https://de
 * Create an integration that represents your app in your Okta org.
 * Add dependencies and configure your mobile app to use Okta.
 * Add a browser-based sign-in flow that Okta controls (redirect authentication).
-* Load the details of the signed in user and check for an existing authenticated session at app startup.
+* Load the details of the signed-in user and check for an existing authenticated session at app startup.
 * Refresh tokens to keep the user signed in.
 * Make server calls using an access token for the session.
 * Test your integration by signing in as a user.
@@ -33,25 +33,26 @@ Make a note of your Okta domain. Use it wherever `${yourOktaDomain}` appears in
 > **Note**: If you're using an existing org, verify that API Access Management is enabled: Open your Admin Console, go to **Security** > **API**, and verify that an **Authorization Servers** tab is present. If not, choose one of the following:
 >
 > * Contact your support team to enable the feature in your org.
-> * Use the Admin Console to create your app integrations instead of the CLI.
+> * Use the Admin Console to create your app integrations.
 >
 
 ## Create an Okta integration for your app
 
 An app integration represents your app in your Okta org. The integration configures how your app integrates with the Okta services. This includes which users and groups have access, authentication policies, token refresh requirements, redirect URLs, and more. The integration includes configuration information required by the app to access Okta.
 
-To create your app integration in Okta using the Admin Console:
+To create your app integration in the Okta Admin Console:
 
-1. [Sign in to your Okta organization](https://developer.okta.com/login) with your administrator account. Click **Admin** on the top right of the page.
-1. Open the apps configuration pane by selecting **Applications** > **Applications**. Click **Create App Integration**.
+1. [Sign in to your Okta org](https://developer.okta.com/login) with your admin account. Click **Admin** on the top right of the page.
+1. Go to **Applications** > **Applications**. Click **Create App Integration**.
 1. Select a **Sign-in method** of **OIDC - OpenID Connect**.
-1. Select an **Application type** of **Native Application**, then click **Next**.
+1. Select an **Application type** of **Native Application**, and then click **Next**.
    > **Note:** If you choose the wrong app type, it can break the sign-in or sign-out flows. Integrations require the verification of a client secret, which public clients don't have.
 1. Enter an **App integration name**.
 1. Enter the callback routes.
 
     <StackSnippet snippet="redirectvalues" />
 
+1. Select the type of **Controlled access** for your app in the **Assignments** section. You can allow all users to have access or limit access to individuals and groups. See [Assign app integrations](https://help.okta.com/okta_help.htm?type=oie&id=ext-lcm-user-app-assign).
 1. Click **Save** to update the Okta app settings.
 
 ## Create an app
@@ -139,7 +140,7 @@ Enable a refresh token in your app integration by following these steps:
 1. Choose **Applications > Applications** to show the app integrations.
 1. Click the name of your integration to open the configuration manager.
 1. Click **Edit** in the **General Settings** section.
-1. Select **Refresh Token** in the **Application** section.
+1. Select **Refresh Token** as the grant type.
 1. Click **Save** at the bottom of the **General Settings** section.
 
 <StackSnippet snippet="refresh" />

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/ios/addconfigpkg.md

@@ -1,16 +1,17 @@
 Add the latest Okta OIDC package to your project:
 
-1. Choose **File** > **Add Packages**. The Swift Package Manager opens.
+1. Choose **File** > **Add Package Dependencies**. The Swift Package Manager opens.
 1. Enter the URL for the package in the search field:
 `https://github.com/okta/okta-mobile-swift.git`
-1. Confirm that the `okta-mobile-swift` package is selected, that the **Dependency Rule** is set to the main branch, and that your project is selected.
+1. Confirm that the `okta-mobile-swift` package is selected, that the **Dependency Rule** is set to the master branch, and that your project is selected.
+1. Click **Add Package**.
+1. Select the package products that appear in the dialog: **AuthFoundation**, **OktaOAuth2**, and **BrowserSignin**, click **Add to target**, and select your project.
 1. Click **Add Package**.
-1. Select the package products that appear in the dialog: **AuthFoundation**, **OktaOAuth2**, and **WebAuthenticationUI**, and then click **Add Package**.
 
 Open `ContentView.swift` and update the `import` statements to use the authorization foundation and WebAuthn UI libraries:
 
 ```swift
 import SwiftUI
 import AuthFoundation
-import WebAuthenticationUI
+import BrowserSignin
 ```

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/ios/checkfortoken.md

@@ -5,7 +5,7 @@ When you check for an existing session, it may take two steps:
 
 The `Credential` class manages the tokens for a user. The `signIn()` function that you wrote in [Open the sign-in page](#open-the-sign-in-page) calls `store(_:)` to save the user's credentials. A session exists if there's a default credential. Although there are calls to check if a credential is expired and to request a refresh, this code uses `refreshIfNeeded()` that only tries to refresh the token if it's expired.
 
-Check for an existing session by adding an `.onAppear` modifier above the `.alert` modifier of the main content view:
+Check for an existing session by adding an `.onAppear` modifier above the `.alert(isPresented:){}` modifier of the main content view:
 
 ```swift
 var body: some View {
@@ -38,6 +38,6 @@ var body: some View {
             busy = false
          }
       }
-      .alert {
+      .alert(isPresented:) {
    ...
 ```

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/ios/configmid.md

@@ -1,4 +1,4 @@
-The SDK loads the configuration values from a configuration file (`Okta.plist`) if it exists in your main bundle. You can also specify the values in the code using `WebAuthentication(issuer:clientId:scopes:redirectUri:logoutRedirectUri:additionalParameters:)`.
+The SDK loads the configuration values from a configuration file (`Okta.plist`) if it exists in your main bundle. You can also specify the values in the code using `BrowserSignin(issuer:clientId:scopes:redirectUri:logoutRedirectUri:additionalParameters:)`.
 
 Create the Okta configuration file and add the keys and values for your app integration:
 

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/ios/opensignin.md

@@ -4,7 +4,7 @@ Update the `signIn()` function of `ContentView.swift` with the code to sign in t
 func signIn() {
    Task {
       do {
-         if let token = try await WebAuthentication.shared?.signIn(from: nil)
+         if let token = try await BrowserSignin.shared?.signIn(from: nil)
          {
             try Credential.store(token)
             updateStatus("Signed in", infoText: "", signedInStatus: true)
@@ -32,7 +32,7 @@ func signOut() {
       do {
          // Show the activity indicator and block UI input.
          busy = true
-         try await WebAuthentication.shared?.signOut(from: nil)
+         try await BrowserSignin.shared?.signOut(from: nil)
          // Remove the stored credential.
          try Credential.default?.remove()
          updateStatus("Signed out", infoText: "", signedInStatus: false)

packages/@okta/vuepress-site/docs/guides/sign-into-mobile-app-redirect/main/ios/refresh.md

@@ -1,6 +1,6 @@
 You refreshed a token when checking for an existing session in [Check for a session at startup](#check-for-a-session-at-startup). In this case you may want to catch any errors that occur.
 
-Update `refreshToken` in `ContentView.swift` with the following code:
+Update the `refreshToken` function in `ContentView.swift` with the following code:
 
 ```swift
 func refreshToken() {
@@ -29,7 +29,7 @@ Tokens are refreshed regularly. Each refresh requires network activity, which is
 * Check if the device is using cellular data rather than Wi-Fi.
 * Handle failed refresh attempts, especially when the server can't be reached.
 
-The `Token` class contains information such as expiry date. The following function displays the access token, its issue and expiry dates, and any associated refresh token in the info area:
+Update the `showTokenInfo` function in `ContentView.swift` with the following code:
 
 ```swift
 func showTokenInfo() {